I'm creating a new table that contains a 'user'. So far, the table looks like:
create table users( id primary key, code varchar )
Currently, the "universe" of codes consists of:
Is it worthwhile, from a DB Design point of view, to create a
codes table that contains all known codes?
create table codes( value varchar, -- with unique constraint description varchar )
Then, I could update my
code column to have a
foreign key relationship to the
Does this change seem to be useful for my above case?