LOL!!!!! :) On Thu, Dec 13, 2012 at 12:36 PM, Thad Esser <[email protected]> wrote: > ** Its always funny how "nothing" can be so confusing. No wonder the Romans > didn't have a zero. :-) > > Thad > > > On Thu, Dec 13, 2012 at 8:51 AM, Mueller, Doug <[email protected]> wrote: >> >> ** >> >> Folks, >> >> >> >> Just to be clear…. >> >> >> >> This is not an AR or SRM topic. It is a Relational Database query topic. >> >> >> >> NULL is a value. It means that there is "no value". >> >> >> >> So, if you search for something in ANY relational database and specify a >> criteria, unless you explicitly test for >> >> NULL values, NULL values will not match. >> >> >> >> Yes, this seems weird that "NULL" will not match when you say "does not >> equal a specific value". But, that is >> >> the nature of relational queries. >> >> >> >> "no value" does not match and does not NOT match ANYTHING. It can only be >> tested for NULL. >> >> >> >> ANY qualification where the value in the DB is NULL will return a FALSE >> for that portion of the qualification >> >> unless the qualification is specifically to test for NULL. >> >> >> Just something to keep in mind whenever you are querying a database. >> >> >> >> Doug Mueller >> >> >> >> From: Action Request System discussion list(ARSList) >> [mailto:[email protected]] On Behalf Of Jason Miller >> Sent: Thursday, December 13, 2012 7:39 AM >> To: [email protected] >> Subject: Re: Qualification syntax question >> >> >> >> ** >> >> You are correct, this happens throughout AR not just SRM. Now that you are >> excluding based on 'Remedy Login ID' you will have to explicitly include >> $NULL$ in the query. >> >> Something like: >> AND ('Remedy Login ID' != $\USER$ OR 'Remedy Login ID' = $\NULL$) >> >> Jason >> >> ** All, >> Need to understand the behavior behind this. It's within SRM but I feel >> the qualification is AR related so any help would be appreciated. >> I have a service that has to do with access. Of course, the requirement is >> that the submitter should not be able to pick themselves as someone who >> needs to get access. There are search menus that allow the submitter to >> narrow down to the person who needs access. The last menu is called Full >> Name and it does a lookup on the People form. Without the requirement of the >> submitter being unable to pick themselves, the menu works fine. However, >> when I add the following to the qualification: >> >> AND 'Remedy Login ID' != $\USER$ >> >> my requirement is met but with side effects. The submitter cannot see >> their name in the drop down but the side effect is that any user who has a >> $NULL$ value in the Remedy Login ID field doesn't show up either. How is it >> that the above string also includes null values? >> >> This is SRM/ITSM/ARS 7.6.04 p1 >> >> -- >> Tauf Chowdhury >> >> >> _ARSlist: "Where the Answers Are" and have been for 20 years_ >> >> _ARSlist: "Where the Answers Are" and have been for 20 years_ >> >> _ARSlist: "Where the Answers Are" and have been for 20 years_ > > > _ARSlist: "Where the Answers Are" and have been for 20 years_
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
