-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, Feb 07, 2001 at 09:50:23AM +0100, Hans-J. Krause wrote:
> A database *never* should accept an insert of an empty string in a not null
> column
Actually, it should. According to SQL-92, '' != NULL. Oracle has threatened to
fix the behavior for quite some time now but it never seems to happen (although
they sure enjoy mentioning it in release notes). I would wager that they're
simply waiting for Oracle9 to make such a broad change to expected program
behavior. Don't count on Oracle doing what it does now forever.
But no matter how one's database treats nulls and empty strings, a space is
neither, and Oracle doesn't treat it as one. The onus seems to be on
DBD::Oracle here.
- --
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/AwUBOoGRfwOGqGs0PadnEQJqzQCfZSY8YMnKkrLVpoYLUswOi77yAKwAoMTy
cI2RbWdUy4Ria5k2oNTN9Ch7
=sLDB
-----END PGP SIGNATURE-----
