Fix compatibility with DBAL 4.x

Open kissifrot opened this issue 1 year ago • 4 comments

Call to Table::addForeignKeyConstraint now expects only a string for the table argument, so ensure we send table name instead of Table object.

Oct 24 '24 18:10 kissifrot

I had to alter the way transactions in deleteAcl() worked, as enabling nested ones are marked as deprecated in DBAL 4.x and make the tests fail :slightly_frowning_face:

Nov 23 '24 10:11 kissifrot

Any progress on this? Or any support needed?

Feb 14 '25 14:02 ronaldvdlp

Can this PR be checked and merged? Would be nice to be able to upgrade to DBAL 4.x!

Aug 15 '25 13:08 ronaldvdlp

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.

Aug 22 '25 20:08 igordeveloper