Stop Using ENUMs in Your Database (Use This Instead)

ENUMs in SQL databases seem convenient for restricting column values, but they come with five significant drawbacks: schema changes require costly ALTER TABLE operations that can lock large tables, values are stored as integers causing sorting and reordering issues, they create vendor lock-in, they can't store extra metadata, and they can't be queried to populate UI dropdowns. The recommended alternative is a separate lookup table with an integer foreign key. This approach allows adding new values via simple INSERT statements without schema changes, supports extra metadata like sort order or display colors, enables easy joins for human-readable labels, and works across any SQL database.