-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dane Foster wrote:
> I'm trying to understand how MySQL behaves in regard to setting a column to NULL
> when the column is defined as being NOT NULL. I've made the assumption that if
> a column's specification says NOT NULL, if I try to set the column's value to
> NULL MySQL would give me an error refusing to do it. I've just tested my
> assumption and I'm wrong. It doesn't complain and worse still it replaces the
> value that existed in the column before I tried changing it to NULL to an empty
> string. Is this behavior correct or a bug?
>
>
>
> Dane Foster
This is by design, see:
http://www.mysql.com/doc/en/Design_Limitations.html
-Mark
- --
MySQL 2003 Users Conference -> http://www.mysql.com/events/uc2003/
For technical support contracts, visit https://order.mysql.com/?ref=mmma
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mark Matthews <mark@stripped>
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Full-Time Developer - JDBC/Java
/_/ /_/\_, /___/\___\_\___/ Flossmoor (Chicago), IL USA
<___/ www.mysql.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.1.90 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD4DBQE+Z7KptvXNTca6JD8RAtwDAJibfm96YdbqZLyWve/e94wYqgurAJ9/h30C
dcuG9QoupX2aEfFr1bYNZw==
=WKEg
-----END PGP SIGNATURE-----
