How does using an ENUM data type in MySQL for storing values from radio buttons affect the flexibility of the database structure?

Using an ENUM data type in MySQL for storing values from radio buttons can limit the flexibility of the database structure because it restricts the possible values to a predefined list. If new options need to be added or existing ones modified, it requires altering the table structure, which can be cumbersome and may lead to data integrity issues. To address this, a better approach would be to use a separate lookup table to store the options and establish a relationship with the main table using foreign keys.

// Create a lookup table for radio button options
CREATE TABLE radio_options (
    id INT PRIMARY KEY,
    option_value VARCHAR(255)
);

// Insert some sample options into the lookup table
INSERT INTO radio_options (id, option_value) VALUES (1, 'Option 1');
INSERT INTO radio_options (id, option_value) VALUES (2, 'Option 2');
INSERT INTO radio_options (id, option_value) VALUES (3, 'Option 3');

// Modify the main table to store a foreign key reference to the radio_options table
ALTER TABLE main_table ADD COLUMN option_id INT,
ADD CONSTRAINT fk_option_id FOREIGN KEY (option_id) REFERENCES radio_options(id);