it's a classic problem of the tradeoff between database normalization and speed. the decisions are guided by the amount of traffic and the type of database you are using. for example if you are using google app engine, where you cannot do joins, i would say 1 table that is completely denormalized. for a traditional SQL style database it depends on the joins and indexes you would need. if you have to join all 6 tables in on each query then it's probably not a great design from a query efficiency standpoint (but would take the least space to store since no data is duplicated).
cfh On Monday, June 11, 2012 7:46:35 AM UTC-7, Hassan Alnatour wrote: > > I think some simple queries nothing complex , i will just sort every > level by its parent . >
