TYPO3 Core

Hi Morton,

As my (newbie) installation don't have that much extensions, I guess it must be fal_securedownload.
Where could I finde the SQL changes an extensions makes during installation?

I have a very, very similar issue for extension kk_csv2table. This extension creates a NOT NULL column tt_content.tx_kkcsv2table_flex. Which also get's a NULL value for each file upload, so, at least for me, unusable. I'll open a seprate issue for that.

Regards,
Michael

Hi Morton,

SOLVED.

I've checked: Both extensions fal_securedownload and e.g. kk_csv2table are adding NOT NULL columns to TYPO3 core tables. fal_securedownload adds, as reported here, SYS_FILE_METADATA.FE_GROUPS TINYTEXT NOT NULL.

The problem was, that my new TYPO3 installation uses an also new MySQL/MariaDB installation which itself uses STRICT SQL mode as default, as all newer MySQL/MariaDB are doing worldwide: https://dev.mysql.com/doc/refman/5.7/en/sql-mode.html

But both extensions and so TYPO3 are "trusting" on the previously set NON-STRICT mode: They add NOT-NULL columns to TYPO3 core/system tables, SYS_FILE_METADATA or TT_CONTENT. As TYPO3 core is, of course, not "aware" of that, all INSERT from TYPO3 core operations be the same as before extension installation and don't add any values to these "unknown" columns. As they are defined as NOT NULL, and MySQl/MariaDB does not allow DEFAULT values on TEXT/TINYTEXT/MEDIUMTEXT columns, "trusting" on "NON-STRICT" mode means that NON-STRICT "allows" inserting a NULL value into a NOT-NULL column, in fact inserting an empty string instead of a NULL value.

"Trusting" on this make it easy for TYPO3 an it's extensions to be independent and flexible, but as this issue shows not following (SQL) standards could mean pitfalls in compatibility, we should at least document this very clearly.

Solution to solve this issue was to set $TYPO3_CONF_VARS[SYS] setDBinit = SET SESSION sql_mode='', (re-)enabling NON-STRICT mode.

I recommend doing this isolated for TYPO3's database user's SESSION. NOT on MySQL's instance level. As not always, and definitively not on my own MariaDB instance, only TYPO3 is using the database instance , and other systems might rely on SQL standards.