MySQL strict mode compatibility

[zonky2]

with MySQL strict mode we have the follow error

An exception occurred while executing 'UPDATE mm_employees SET alias = ? WHERE id = ?' with params [null, 80]:

SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'alias' cannot be null

we can include serializeData with

    public function serializeData($value)
    {
        return $value === null ? '' : $value;
    }

or we change getSQLDataType and set default to NULL

btw: if we change the default from '' to NULL, we must write a updating script - or not?

[richardhj]

Allowing null should be fine.

[zonky2]

Allowing

hmm? is not the question whether we set NULL or '' as default? and not whether we allow what or not...

[zonky2]

discussed with @discordier: we set default to NULL - also for other text based attributes; we have to create an updater yet

[Ainschy]

there is a issue when you use force_alias

UPDATE mm_metamodel SET alias = ? WHERE id = ?' with params [null, 5]: SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'alias' cannot be null

[discordier]

@Ainschy This is already fixed in #29, we need the migration though to finish it. This is on hold until we have https://github.com/contao-community-alliance/contao-polyfill-bundle/pull/2 out of the door.

[zonky2]

fixed