As far as a relational lookup vs. enums go, if enums can only be modified by a DBA using drop/create then that's a huge downside. If the values are in a lookup table those values can potentially be edited by an administrator in the UI of the application. For this reason alone enums are a non-starter for me. The only time they would be useful is if there is a well defined and unchanging set of values.
@TheMagicofSQL4 күн бұрын
Thanks for your thoughts In general enums are only suitable for small, static lists of values. If you expect the values to change regularly you should stick with a lookup table. That said, we'll discuss enhancing enums to allow you to add values to the list.