Re: So what's null then if it's not nothing?

On Wed, 23 Nov 2005 09:20:32 +0100, Jon Heggland wrote:

>In article <kfa7o1d714eqdnlfnaik6t1gs6uv4l0b09_at_4ax.com>,
>hugo_at_pe_NO_rFact.in_SPAM_fo says...
>> >2- You create a parent/root entity/table and make a subtype for each
>> >optional field
>>
>> And that would lead to an exponential explosion of tables. With one
>> optional attribute, you get two subtypes. Two optional attributes means
>> four subtypes. With 10 optional attributes, you'd need no less than
>> 1,024 tables.
>
>You mean you would create a table for each *combination* of attributes?
>What on earth for?

Hi Jon,

I wouldn't. It's a suggestion that has been made in this thread as a way to model the data without the need for NULLs. I merely pointed out the weak spot in this method.

Best, Hugo

-- 

(Remove _NO_ and _SPAM_ to get my e-mail address)