Thom, If you want to use a "standard", it should be OFF. Then you conform to the 3-value logic of the SQL Standard: a null (or unknown) value cannot be considered "equal" or "not equal" to any other value, not even another null (or unknown) value. It is tested with the operators "IS NULL" and "IS NOT NULL." Setting EQNULL ON is for your own convenience, if you have a hard time figuring out how to design your database and code you applications within that standard.
Bill On Mon, 22 Jul 2002 22:27:11 -0400, Thomas J Cimicato wrote: >What is the prevailing thought on the use of the EQNULL setting?? >Should you code for it ON or OFF as a standard? (Off seems to be the >default in the rbase.cfg file. ) ================================================ 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/
