[TYPO3-core] RFC #4693: tables definition not compliant with MySQL 5.0 strict mode

Oliver Klee typo3-german-02 at oliverklee.de
Mon May 12 17:09:52 CEST 2008


Dmitry Dulepov [typo3] schrieb:
> Is there any varchar definitions with NOT NULL and without DEFAULT? 

I was thinking of cases like this:

-  non_exclude_fields text NOT NULL,
-  explicit_allowdeny text NOT NULL,
+  non_exclude_fields text,
+  explicit_allowdeny text,
    allowed_languages varchar(255) DEFAULT '' NOT NULL,

Shouldn't this be changed to:

    allowed_languages varchar(255),

... so the definitions for string fields (in the broader sense) are 
consistent?


Oliver


More information about the TYPO3-team-core mailing list