-
-
Notifications
You must be signed in to change notification settings - Fork 52
Fix compatibility with DBAL 4.x #122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
2afa233
to
b872aaf
Compare
c6c44e2
to
60d3470
Compare
60d3470
to
f50a430
Compare
I had to alter the way transactions in |
Any progress on this? Or any support needed? |
Can this PR be checked and merged? Would be nice to be able to upgrade to DBAL 4.x! |
public function deleteAcl(ObjectIdentityInterface $oid) | ||
{ | ||
$this->connection->beginTransaction(); | ||
// DBAL 4.0 does not support nested transactions, so we need to keep track of the transaction state |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
DBAL 4.0 does not support nested transactions
Yes, it does?
Hi @nicolas-grekas . Do you have any news about this issue, can estimate a date for release with support sf7 + doctrine dbal 4+? Thank you. |
Call to Table::addForeignKeyConstraint now expects only a string for the table argument, so ensure we send table name instead of Table object.