Update doctrine/dbal to 2.5.5

[DeepDiver1975]

Description

doctrine/dbal 2.5.5 has just been released

Motivation and Context

stay up to date with our libs

How Has This Been Tested?

Jenkins will do the job

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[PVince81]

Ouch, DB-related test failures

[butonic]

👍 phew

[butonic]

backport to 9.1? to 9.0.x?

[DeepDiver1975]

backport to 9.1? to 9.0.x?

any reason to do so?

[butonic]

customers with oracle are trying to move to php7 because the php5.5 they are currently using is EOL but their enterprise distros basically skip 5.6. I had hoped 2.5.5 would already contain the necessary oracle fixes, but ... they don't, yet: #18425 (comment) If dbal 2.6 is available we might need to backport to 9.1 at least ... if we still support it by then.

[DeepDiver1975]

If dbal 2.6 is available we might need to backport to 9.1 at least

Let's see once we get there ... but until then: I consider backporting dbal as too critical.
Oracle and php7 users need to use 9.2 (assuming we get dbal 2.6 within the release schedule of oc9.2)

[DeepDiver1975]

Oracle and php7 users need to use 9.2 (assuming we get dbal 2.6 within the release schedule of oc9.2)

let's see what dbal devs say - doctrine/dbal#2468 (comment)

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.