Displaying 1 result from an estimated 1 matches for "user_other_fields".
2006 Jun 12
4
Modelling: A table of domains
Greetings!
I''m thinking of setting up a table of "domains", consisting of the core
fields id, code, name, description, and type. Users is a domain, orders
is a domain, recipes is a domain, etc. Domain attributes other than
those covered by the core fields will go to, say, a user_other_fields
table, recipe_other_fields, etc. I see the advantage of having all
"things" in the database in one table. But there could be design
disadvantages, and also Rails implementation disadvantages. Anyone has
had experience in this area? Thank you for your thoughts.
joshi
--
Posted via ht...