Yes...in theory you are certainly correct. Very well explained, by the way. But in practice it doesn't seem to be the case with Remedy. Doug says it should be the case because the filter just passes the query to the underlying DB and awaits the result, but...
________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Cupp, Michael E Jr. CTR USAF AFRL/SNOD Sent: Friday, June 15, 2007 11:54 AM To: arslist@ARSLIST.ORG Subject: Re: $NULL$ != $NULL$ I'm not an MS SQL Guy, but 15+ years in Oracle. Null (in Oracle) essentially means 'I don't know the value'. I.e - If I have 2 values, A and B. If A and B are both 0, then I know that A=0 and B=0, therefore A=B If either A or B is null, I can say A=0, B=null or 'I don't know the value of B'. Therefore, I cannot say that A=B, so I must assume that A <> B. Works for both null is well. If I don't know the values for A and B, how can I know they are the same? ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Guillaume Rheault Sent: Friday, June 15, 2007 11:16 AM To: arslist@ARSLIST.ORG Subject: Re: $NULL$ != $NULL$ ** Tab, Actually null means literally zero in German. The spelling in French is nul (one L) Guillaume ________________________________ From: Tab Merkel Sent: Thu 06/14/07 3:48 PM To: arslist@ARSLIST.ORG Subject: Re: $NULL$ != $NULL$ Actually its deeper than SQL...Not so much an SQL thing... The root (French) meaning of NULL is: not any Which means NULL != anything. And anything includes NULL. Quoting Warren Baltimore <[EMAIL PROTECTED]>: > I'm not really sure about this, but I think this is actually how SQL handles > null=null...Not so much a Remedy thing... > > Any SQL gurus out there care to explain this one? > > > On 6/14/07, Opela, Gary L Contr OC-ALC/ITMA <[EMAIL PROTECTED]> > wrote: >> >> ** >> >> What they will say is that they have fixed a bug, not that they've broken >> your code. >> >> >> >> I have run into this in the past, where I had to write remedy >> functionality designed around, or using their bugs, then they fix it and >> break the functionality. Some bugs, I guess, are just best left in the >> product. >> >> >> ------------------------------ >> >> *From:* Action Request System discussion list(ARSList) [mailto: >> [EMAIL PROTECTED] *On Behalf Of *Kaiser Norm E CIV USAF 96 CS/SCCE >> *Sent:* Thursday, June 14, 2007 8:26 AM >> *To:* arslist@ARSLIST.ORG >> *Subject:* Re: $NULL$ != $NULL$ >> >> >> >> So any code written for 5.1.2 now may have defects in it that are >> introduced simply by upgrading. >> >> >> ------------------------------ >> >> *From:* Action Request System discussion list(ARSList) [mailto: >> [EMAIL PROTECTED] *On Behalf Of *Warren Baltimore >> *Sent:* Wednesday, June 13, 2007 4:02 PM >> *To:* arslist@ARSLIST.ORG >> *Subject:* Re: $NULL$ != $NULL$ >> >> >> >> ** Nope Norm, I don't think your crazy! I believe your on the money. >> >> On 6/13/07, *Kaiser Norm E CIV USAF 96 CS/SCCE* <[EMAIL PROTECTED]> >> wrote: >> >> ** >> >> I may be crazy, but I seem to recall from the dark recesses of my mind >> that when comparing values, if two values are $NULL$, the expression would >> evaluate to FALSE. That's the way it seemed to work at least up to v5.1.2 >> . >> >> >> >> For example, suppose I have form A and form B and I do a PUSH FIELDS from >> A to B if field1on A is equal to field2 on B. As I recall-and I'm pretty >> certain this is true-if field1 is NULL and field2 is NULL, the PUSH FIELDS >> qualification fails because it evaluates to FALSE. >> >> >> >> It seems with version 6.3 (and higher?) this type of expression now >> evaluates to TRUE??? >> >> >> >> Am I crazy? >> >> __20060125_______________________This posting was submitted with HTML in >> it___ >> >> >> >> >> -- >> Warren R. Baltimore II >> Remedy Developer >> UW Medicine IT Services >> School of Medicine >> University of Washington >> Box 358220 >> 1325 Fourth Ave, Suite 2000 >> Seattle, WA 98101 >> >> The opinions expressed in this e-mail are in no way those of the >> University of Washington, or the State of Washington. They are my own. >> __20060125_______________________This posting was submitted with HTML in >> it___ >> __20060125_______________________This posting was submitted with HTML in >> it___ __20060125_______________________This posting was submitted with HTML >> in it___ > > > > > -- > Warren R. Baltimore II > Remedy Developer > UW Medicine IT Services > School of Medicine > University of Washington > Box 358220 > 1325 Fourth Ave, Suite 2000 > Seattle, WA 98101 > > The opinions expressed in this e-mail are in no way those of the University > of Washington, or the State of Washington. They are my own. > > ________________________________________________________________________ _______ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > ARSlist:"Where the Answers Are" ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"