Ensure post transaction callbacks are only at the end of the root Drupal transaction

Created on 14 April 2024, 8 months ago
Updated 18 September 2024, 3 months ago

Problem/Motivation

Ensure post transaction callbacks are always executed ONLY at the end of the root Drupal transaction.

Proposed resolution

We need to keep track of the very first 'root' transaction object created, because under some circumstances we might end up processing more than one of them during the transaction stack lifecycle.

For example, a root transaction is opened, then a DDL statement is executed in a database that does not support transactional DDL, and another root opened before the original one is closed. By having the first one tracked, we can ensure that post transaction callbacks are processed only upon its destruction and not before.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

🐛 Bug report
Status

Fixed

Version

10.3

Component
Database 

Last updated 2 days ago

  • Maintained by
  • 🇳🇱Netherlands @daffie
Created by

🇮🇹Italy mondrake 🇮🇹

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024