Thanks To All! I was indeed looking for the prevailing thought on the issue without necessarily resurrecting the entire discussion. All the comments were incredibly helpful to my understanding of this topic. Bill's comment (well said good man!) regarding the 3 value logic of the SQL standard is something I will have to learn and standardize to. I currently lean toward EQNULL ON and ZERO ON, however, to do table joins properly, EQNULL needs to be OFF as it seems.
In my recent conversion from 4.5++ to 6.5++, this topic needed to come into focus for me since it works differently/correctly in 6.? Thank you to all who quickly made this clear for me. I can now proceed forth well advised. Warmest Regards, (as Tom Grimshaw always says :) Thom Cimicato BTW!!! R:Base 7.0 ROCKS!!! At 09:13 AM 07/24/2002 -0400, you wrote: >Bill, > >Well said!! This discussion seems to popup now and then on this >forum. I seem to recall that Microrim put this feature in to >accommodate one of its biggest customers. Perhaps it is time >to move this feature into the "undocumented" category and eventually >remove it from RBase. I for one have this set to OFF and try >as much as possible to adhere to coding to SQL standards. > >-- >Jim Bentley >American Celiac Society >[EMAIL PROTECTED] - email >(973) 325-8837 voice >(973) 669-8808 Fax > > >---- "Bill Downall" <[EMAIL PROTECTED]> wrote: > > 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/ > > >================================================ >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/ ================================================ 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/
