| Subject: | Handling of undef/NULL values |
I wonder if undefined values should be handled by using "... IS NULL".
That is, the call to
sql_interp({bla => undef})
should return
(" bla is NULL", ())
rather than
(" bla =?", (undef))
Unfortunately such a change would probably be incompatible because users
might assume that undef is handled the same as the empty string.
Also, the DBI documentation mentions some incompatibilities in handling
NULL values between database drivers (see the "Null values" section).
Regards,
Slaven