I compeelty agree a denormailzed database schema is not a bad design in some cases, ecspecially when performance is considered UPC desc in asumarray table for example, but Niel said puting a comma seperated list does not break any 'rules' I was simpley making a point it does break a rule, not jsut a 'rule' but a rule.
Adam H On Fri, 25 Feb 2005 09:51:18 -0500, Michael T. Tangorre <[EMAIL PROTECTED]> wrote: > > From: Adam Haskell [mailto:[EMAIL PROTECTED] > > This is going to get off topic butany time you want to find > > an idividual value in this comma seperated list your design > > begins to enter the bad design area. And it does break > > normailization rules... > > I knew this topic was gonna last about 10 seconds before going off-topic :-) > Anyway, we should remember that a good DB is not necessarily a fully > normalized one. Sometimes it makes sense to denormalize some to improve > performance. I doubt that this is the case here, but you never know... we > don't have the reasoning behind the design choices. > > ok, back to topic. :-) > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:196530 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
