Carsten, Thanks for the answer (and other thanks go to the other guys that answered me).
I think normalization is the way to go. I think it is the right thing to do (in theory). The problem is that theory doesn't fit all. Basically I have some tables with only 2 fields (ID and name), and a central table, joined by a one-to-many relation. The key point here are the 2-field tables. If I keep them separate, I can extend them (add new fields) without problem when need arise. But if there is no need for an extension (my case), all I get is a greater number of tables that I have to take care of. Wouldn't be better (maybe more efficient ?) to put all the 2-field tables in only table, with a separate ENUM field to separate the records on categories ? -- Cip CRD> Hi Ciprian, CRD> OK, I'm by no means a DB guru, so a) take this with a grain of salt CRD> and b) feel free to tear it apart if I'm completely wrong! ;] CRD> If in fact your people and city tables aren't going to change very CRD> often, then why don't you just go all the way and keep that CRD> information somewhere else in your application and write it straight CRD> to your travel_expenditures table, e.g.: [..] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
