> From: Sterin, Ilya [mailto:[EMAIL PROTECTED]] > > So if NULL is not defined, what's the difference between "is NULL" and > "=NULL". I guess my disagreement comes from not being able to ask for > undefined field by =undefined, but rather is undefined. It's
It is all a matter of being theoretical, but when it comes down to practicality, it'd be easier if we could just say '=NULL'. But when you think about it, even in perl (as an effort to keep this somewhat OnTopic :), we can't say '== undef' or 'eq undef' (we can but it doesn't do what we mean), so we have to say 'defined(...)', so the universe is at least consistent in this respect, if a bit inconvienient. Or you can always write to every database vendor, and ANSI, and get them all to support '=NULL' :-) Cheers, Douglas Wilson
