Displaying 1 result from an estimated 1 matches for "rock_id".
Did you mean:
lock_id
2006 May 22
6
existing magic to prevent db redundancy?
suppose users have a favorite colour, linked to with a color_id field.
suppose also they have a pet rock, which is one of many possible
colors...
is there a ''best practice'' in order to avoid having ''blue'' appear in the
Color table 100 times. can validates_uniqueness_of be twisted into
handling this case? should i be adding something to the initialize()