doctrine/archived-orm
1
0
Fork 0
mirror of https://github.com/doctrine/orm.git synced 2026-03-24 06:52:09 +01:00
Code Issues 5.3k Packages Projects Releases 100 Wiki Activity

Temporary tables vs MysQL GTID consistency #6230

New Issue
Closed
opened 2026-01-22 15:29:17 +01:00 by admin · 3 comments
admin commented 2026-01-22 15:29:17 +01:00
Owner
Copy Link

Originally created by @arnaud-lb on GitHub (May 2, 2019).

Originally assigned to: @Ocramius on GitHub.

Bug Report

Q A
BC Break yes
Version ^2.6

Summary

OneToManyPersister uses CREATE TEMPORARY TABLE when removing orphaned collections, which is not allowed in MySQL when using global transaction IDs.

Global transaction IDs is a feature that makes operating MySQL much easier when using replication. It is enabled server-wide. I suspect that it is very common that this feature is enabled on production servers.

Current behavior

When a OneToMany full collection is replaced, the following exception occurs:

PDOException: SQLSTATE[HY000]: General error: 1787 When @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1, the statements CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can be executed in a non-transactional context only, and require that AUTOCOMMIT = 1. These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions. in .composer/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOConnection.php:57

Full trace here: https://gist.github.com/arnaud-lb/31b20963b01ff2ccc8b1bcd5f75fc461

Originally created by @arnaud-lb on GitHub (May 2, 2019). Originally assigned to: @Ocramius on GitHub. ### Bug Report | Q | A |------------ | ------ | BC Break | yes | Version | ^2.6 #### Summary OneToManyPersister uses `CREATE TEMPORARY TABLE` when removing orphaned collections, which is not allowed in MySQL when using global transaction IDs. Global transaction IDs is a feature that makes operating MySQL much easier when using replication. It is enabled server-wide. I suspect that it is very common that this feature is enabled on production servers. #### Current behavior When a OneToMany full collection is replaced, the following exception occurs: ``` PDOException: SQLSTATE[HY000]: General error: 1787 When @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1, the statements CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can be executed in a non-transactional context only, and require that AUTOCOMMIT = 1. These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions. in .composer/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOConnection.php:57 ``` Full trace here: https://gist.github.com/arnaud-lb/31b20963b01ff2ccc8b1bcd5f75fc461
admin added the BugCan't Fix labels 2026-01-22 15:29:17 +01:00
admin closed this issue 2026-01-22 15:29:17 +01:00
admin commented 2026-01-22 15:29:18 +01:00
Author
Owner
Copy Link

@Ocramius commented on GitHub (May 3, 2019):

This is not fixable: as per 1587aac4ff, this is required for Joined Table Inheritance and OneToMany associations in orphanRemoval.

Since the GTID consistency is a niche, I'm gonna mark this as "can't fix". If an alternate approach (to 1587aac4ff) is needed, then we'd need that first.

@Ocramius commented on GitHub (May 3, 2019): This is not fixable: as per https://github.com/doctrine/orm/commit/1587aac4ff6b0753ddd5f8b8d4558b6b40096057, this is required for Joined Table Inheritance and OneToMany associations in `orphanRemoval`. Since the GTID consistency is a niche, I'm gonna mark this as "can't fix". If an alternate approach (to 1587aac4ff6b0753ddd5f8b8d4558b6b40096057) is needed, then we'd need that first.
admin commented 2026-01-22 15:29:18 +01:00
Author
Owner
Copy Link

@KVestergaard commented on GitHub (Nov 10, 2023):

This is not fixable: as per 1587aac, this is required for Joined Table Inheritance and OneToMany associations in orphanRemoval.

Since the GTID consistency is a niche, I'm gonna mark this as "can't fix". If an alternate approach (to 1587aac) is needed, then we'd need that first.

Not a niche any more. Azure (and others) require enforced gtid compliance for replication (e.g. geo-replication for HA).

@KVestergaard commented on GitHub (Nov 10, 2023): > This is not fixable: as per [1587aac](https://github.com/doctrine/orm/commit/1587aac4ff6b0753ddd5f8b8d4558b6b40096057), this is required for Joined Table Inheritance and OneToMany associations in `orphanRemoval`. > > Since the GTID consistency is a niche, I'm gonna mark this as "can't fix". If an alternate approach (to [1587aac](https://github.com/doctrine/orm/commit/1587aac4ff6b0753ddd5f8b8d4558b6b40096057)) is needed, then we'd need that first. Not a niche any more. Azure (and others) require enforced gtid compliance for replication (e.g. geo-replication for HA).
admin commented 2026-01-22 15:29:19 +01:00
Author
Owner
Copy Link

@Ocramius commented on GitHub (Nov 10, 2023):

@KVestergaard open a new issue please: this is 4 years old, and the context may have changed.

@Ocramius commented on GitHub (Nov 10, 2023): @KVestergaard open a new issue please: this is 4 years old, and the context may have changed.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
BC Break
Bug
Can't Fix
Deprecation
Documentation
DQL
Duplicate
Failing Test
Hacktoberfest
Improvement
Improvement
Incomplete
Invalid
Missing Tests
New Feature
PR Created
pull-request
Mirrored from GitHub Pull Request
 Question
Regression
Status: Waiting feedback
Waiting feedback
WIP
Won't Fix
No Label Bug Can't Fix
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
admin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: doctrine/archived-orm#6230
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?