Re: So what's null then if it's not nothing?
From: Jon Heggland <heggland_at_idi.ntnu.no>
Date: Wed, 23 Nov 2005 14:40:28 +0100
Message-ID: <MPG.1dee8fb2729d5101989707_at_news.ntnu.no>
Date: Wed, 23 Nov 2005 14:40:28 +0100
Message-ID: <MPG.1dee8fb2729d5101989707_at_news.ntnu.no>
In article <438456fe$1_at_news.fhg.de>, spam_at_conceptoriented.com says...
> > You mean you would create a table for each *combination* of attributes?
> > What on earth for?
>
> In order to avoid nulls (there is an opinion that they need to be
> removed from schema).
I get that part. But why one for each combination? Why not just one per attribute?
-- JonReceived on Wed Nov 23 2005 - 14:40:28 CET