The trigger on sonata_event's tsv column is not running if a transaction has multiple inserts in it. I'm guessing that this behavior also happens if the transaction has multiple updates. Rework the trigger and the check if a constraint trigger will do the job. This, however would result in a breaking change, preventing users of previous releases from updating directly to v2.0.
The trigger on sonata_event's tsv column is not running if a transaction has multiple inserts in it. I'm guessing that this behavior also happens if the transaction has multiple updates. Rework the trigger and the check if a constraint trigger will do the job. This, however would result in a breaking change, preventing users of previous releases from updating directly to v2.0.