You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
minor #61582 [DoctrineBridge] Use a single table in isSameDatabaseChecker (GromNaN)
This PR was squashed before being merged into the 7.4 branch.
Discussion
----------
[DoctrineBridge] Use a single table in isSameDatabaseChecker
| Q | A
| ------------- | ---
| Branch? | 7.4
| Bug fix? | yes
| New feature? | yes
| Deprecations? | no
| Issues | Fix#54348
| License | MIT
The `isSameDatabaseChecker` feature of the SchemaListener detect if 2 DBAL connections are connected to the same server and database by creating a temporary table with one connection and checking if the table exists using the other connection.
Creating a temporary table with a random name cause an issue to configure permissions, as an exhaustive list of table names can be required.
I propose to modify the implementation to always use the same table name, but insert a row with a random key with one connection and try to delete it with the other connection.
The table is dropped only if it is empty, to prevent concurrence issues.
Commits
-------
e2cc570 [DoctrineBridge] Use a single table in isSameDatabaseChecker
0 commit comments