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
denormal
I think some simple queries nothing complex , i will just sort every level
by its parent .
What kind of queries are you planning to run on this data?
Your answer will help us decide whether this is better to have in few
or many tables.
Also of relevance are the normal forms
(http://en.wikipedia.org/wiki/Database_normalization)
On Tue, Jun 12, 2012 at 12:39 AM, Hassan Alnatour
wrote:
3 matches
Mail list logo
