riginal Message-
> From: Jesse, Rich [mailto:[EMAIL PROTECTED]]
> Sent: 14 October 2002 18:34
> To: Multiple recipients of list ORACLE-L
> Subject: No Nulls? (was: Warehouse design: snowflake vs star schemas)
>
>
> On the link below is this quote from C.J.Date:
>
10/14/2002 12:58 PM
Please respond to ORACLE-L
To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
cc:
Subject: Re: No Nulls? (was: Warehouse design: snowflake vs star
schemas)
Rich,
I piqued my own curiosity and looked at "Database
But from a practical, operational standpoint, NULLable columns can cause
problems, the least of which is lack of index-ability (for lack of a better
term) when issuing queries containing NOT NULLs and the like. Of course one
might say that one should know the database one is issuing a query agains
Rich,
I piqued my own curiosity and looked at "Database Programming and Design
On-Line". Below is a link to a lengthy response (1995) by Date and others
to Tom Johnston's article defending MVL (Multi-Valued Logic). Plenty to
chew on.
http://www.dbpd.com/vault/dateresp.htm
Jack C. Applewhite
Rich,
Several years ago in the old "Database Programming and Design" magazine (a
really useful publication, IMHO - too bad it's gone), C. J. Date and
another database guru (I can't remember his name) carried on a debate that
lasted several months about the "badness" (Date) vs "goodness" (the oth
4/2002 10:33 AM
Please respond to ORACLE-L
To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
cc:
Subject:No Nulls? (was: Warehouse design: snowflake vs star schemas)
On the link below is this quote from C.J.Date:
"I don't want you
On the link below is this quote from C.J.Date:
"I don't want you to think that my SQL solution to your problem means I
advocate the use of nulls. Nulls are a disaster."
Of course, he doesn't expound upon it (probably not a need except for
dummies like me). Anyone care to comment? (On the quot
