Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> comp.databases.theory -> Re: So what's null then if it's not nothing?

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

From: Jon Heggland <heggland_at_idi.ntnu.no>
Date: Wed, 23 Nov 2005 09:20:32 +0100
Message-ID: <MPG.1dee44bf78fb681f989706@news.ntnu.no>


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?

-- 
Jon
Received on Wed Nov 23 2005 - 02:20:32 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US