If you have 3 tables, then there is no performance impact. I'd keep it normalized.
-----Original Message----- From: Koo Pai Lao [mailto:[EMAIL PROTECTED]] Sent: October 5, 2001 4:54 PM To: CF-Talk Subject: Database Design Question ok, this is just a small example of what I am working with. I have 3 tables, and their relationship is hierarchical. TableA - id, name, year TableB - id, description, TableA_id TableC - id, time, location, TableB_id ok, here is my question. First off, i can relate information from TableA with TableC through TableB, using outer joins or what not. My question is, would it save CPU time if I set up TableC like this... TableC - id, time, location, TableB_id, TableA_id so that I dont have to go through TableB to relate information between TableA and TableC in my SQL statements?? Also, right now my head is telling me that that might be a bad idea, since now if I edit the TableA_id in TableB, i have the burden of editing it in TableC too. But what are your thoughts? I'm just worried that too many wierd SQL statements will take more processing time. Ex.. Select this from there where b.id is c.id AND c = d AND c.id = b.id and c.id = (u get the idea!!) VS. Select a from x where y = z (very simple!) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Get the mailserver that powers this list at http://www.coolfusion.com FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
