Andrew Cleland wrote:
Approach C, have a new status look up table, which would have an id column and a description, and the products table would then have a status id, which if the description was required would include the status table in the find. This seems a bit over the top but maybe is the cleanest way and status can be added and descriptions changed without any changes to application code.
This works well in conjunction with Trevor Squires' acts_as_enumerated
plugin. Using this, statuses are stored in the DB as ids, tested in
code using symbolic name fields, and displayed in views as either the
name field or a separate description field: