On Wed, 24 Jul 2002 13:26:54 -0400, Thomas J Cimicato wrote: > Bill's comment (well said good man!)
Thanks for the kind words, Thom and Jim, but it's true that the definition of null and the 3-value logic (boolean true, false, and unknown) of SQL is certainly the most controversial part of the standard. That's why so many implementations of the standard have a work-around of some kind or other. Thom, as far as database design, you can make some of the controversy moot by defining a "no value entered" value for most of your lookup tables (e.g. Zero for integer keys, and 'N/A' for text keys), and making that the default for the foreign key columns, and then also setting a not null constraint on them. Bill ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
