- Issue created by @mondrake
- ๐ณ๐ฑNetherlands daffie
+1 for me.
I really dislike
unset($transaction);
for the implicit commit. - Status changed to Needs review
about 1 year ago 5:08pm 3 November 2023 - First commit to issue fork.
- Status changed to Needs work
about 1 year ago 3:43pm 21 November 2023 - ๐บ๐ธUnited States smustgrave
Rebased to run the pipeline and it was all green
Ran the test-only feature and they all seemed to still pass shouldn't the base test file fail? https://git.drupalcode.org/issue/drupal-3398767/-/jobs/374406
Seems like something that could use a change record right?
- Status changed to Needs review
about 1 year ago 4:58pm 21 November 2023 - ๐ฎ๐นItaly mondrake ๐ฎ๐น
It should in this case, but I donโt think #3395977-4: Test-only changes reverts changes to test modules โ was addressed and here the change was to a test base class that got reverted too?
- Status changed to Postponed
about 1 year ago 8:10pm 8 December 2023 - ๐ฎ๐นItaly mondrake ๐ฎ๐น
Need to postpone on ๐ Leaving the savepoint in the transaction stack upon rollback is incorrect Needs review
- Status changed to Needs work
about 1 year ago 10:24am 11 December 2023 - Status changed to Postponed
about 1 year ago 5:14pm 11 December 2023 - ๐ฎ๐นItaly mondrake ๐ฎ๐น
Postponed on โจ [PP-1] Introduce a Connection::executeDdlStatement method Active . That will give us the possibility to know about an autocommit due to lack of transactional DDL support having happened BEFORE actually attempting a commit on the DB, and appropriate test coverage, too.
Also we probably need to split the cleanup of
DriverSpecificTransactionTestBase
- there's a lot of bolierplate that was accumulated by copy/pasting test methods that can be removed. - ๐ฎ๐นItaly mondrake ๐ฎ๐น
Filed ๐ Cleanup DriverSpecificTransactionTestBase Needs review .
- ๐ฎ๐นItaly mondrake ๐ฎ๐น
Note to self: when this is unblocked, do #3386263-10: Ignore, testing issue โ first thing.
- ๐บ๐ธUnited States moshe weitzman Boston, MA
We now have
\Drupal\Core\Database\Database::commitAllOnShutdown
. Should we keep this issue open or change it somehow? - Assigned to mondrake
- Status changed to Needs work
4 days ago 5:24pm 17 December 2024 - ๐ฎ๐นItaly mondrake ๐ฎ๐น
Green on all three core supported databases! Ready for review.
I am bumping to Major as it's known there are problems with the current handling of autocommit in HEAD.
The Needs Review Queue Bot โ tested this issue. It fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide โ to find step-by-step guides for working with issues.