Re: So what's null then if it's not nothing?
Date: Wed, 23 Nov 2005 16:02:03 +0100
>>>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
Yes, there are several alternative designs:
Probably there could be also other designs that allow us to avoid nulls.
Probably there could be also other designs that allow us to avoid nulls.The above cases could be considered standard patterns while in general case we would mix them and apply in a generalized form.