-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, Oct 23, 2001 at 09:39:55AM -0600, Sterin, Ilya wrote: > Ok, this might be a silly one. Though I have no problem solving this issue > by dynamically building the query, there should be a better solution due to > repreparing the statement... > > Within the where clause of the query that is prepared...' > > where foo = ? > > When binding an undef value when executing, this executes "where foo = > NULL". In Oracle there is a difference between foo = NULL and foo is NULL.
This is not Oracle, but ANSI-standard behavior. NULL represents the absence or non-existence of a value. A non-existent value cannot be equal to anything. So this is the correct behavior. I personally don't think DBI should muck with proper behavior. (Now, Oracle has that annoying behavior of treating the zero-length string as NULL, which ANSI explicitly says *not* to do...but that's another story.) - -- Stephen Clouse <[EMAIL PROTECTED]> Senior Programmer, IQ Coordinator Project Lead The IQ Group, Inc. <http://www.theiqgroup.com/> -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.8 iQA/AwUBO9WqfQOGqGs0PadnEQLp4QCgjkQkorg5yZyFo1ZoPXjMNehCBK0An0s6 qlEfwtFGaihJDk6L1zsYECwy =BJVL -----END PGP SIGNATURE-----
