Review main Merged

78107[BUGFIX] Avoid "field doesn't have a default value" sql error

Stefan Bürk CR +2 V +2 Easy +1 −0 updated 03/13/23, 16:05

Commit message

Creating new `ext:reactions` records are broken and emits an
sql error message. This happens when it's tried to switch to
the core-shipped type.

>> 2: SQL error: "Field 'fields' doesn't have a default value"

Using a default value on database level does not work with
all database backends TYPO3 v12 officially supports, which
has been tried with #100088 and mitigated with #100101. So
that's not an option here.

This change bakes the default value for `json` type fields
using TCA default setting again, which has been the way the
original `type=user dbType=JSON` variant used with #99226.

Review

  • Code review CR +2

    Imported before Forger kept the single votes, the next import adds them.

  • Verified V +2

    Imported before Forger kept the single votes, the next import adds them.

Issues 5

Files 1