[TYPO3-core] FYI: Bug fixed: "NOT NULL" removed from SQL gives error

[Dmitry Dulepov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi!

Ingmar Schlecht wrote:
> The reason is, that MySQL 5.0 doesn't report anymore whether or not
> fields have the NOT NULL attribute. That resulted in huge lists of
> "Fields to update" in the install tool database analyser like this:
> 
> 	Current value: crdate int(11) DEFAULT '0',
> 	New value    : crdate int(11) DEFAULT '0' NOT NULL,

Yep. I have similar problem. Pre-this-weekend EM always wants to modify
"VARCHAR(255) NOT NULL" to "text". If I set field to TEXT NOT NULL using
mysql tools, EM says it is "TEXT NOT NULL" and proposes "text" as type.
So I never have up-to-date extension with EM :) I neither want text, nor
"TEXT NOT NULL", I want "VARCHAR(255) NOT NULL".

Happens with mysql 4.1.13 from default suse 10 installation. Is it related?

Dmitry.
- --
"It is our choices, that show what we truly are,
far more than our abilities." (A.P.W.B.D.)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)

iD8DBQFEJ85JRVcYnKJ8N6kRAnnHAKCsQl0ilci3GPlebP8/xWAgo42RtACfQeil
RIrJSNnXs4LVYjzNsl+4zp0=
=eUbu
-----END PGP SIGNATURE-----