[TMP] IBX-12043: Upgraded to Doctrine DBAL 4

[ViniTou]

🎫 Issue	IBX-12043

Related PRs:

• [TMP] IBX-12043: Upgraded to Doctrine DBAL 4 core#800 (must merge first)
• IBX-12043: Upgraded to Doctrine DBAL 4 doctrine-schema#45 (must merge first)
• [TMP] Run regression for IBX-12043 (DBAL 4) commerce#1922 (regression run)

Important

composer.json carries [TMP] pointers for ibexa/core and ibexa/doctrine-schema (dev-dbal-4-upgrade as 6.0.x-dev). Both must be reverted to ~6.0.x-dev once those PRs merge, before this PR is mergeable.

Description:

ibexa/core pins doctrine/dbal, so DBAL 4 arrives here whether or not this package was ported. One call site is affected: invitationExistsForEmail() built SELECT 1 by passing the integer 1 to select(), which DBAL 4 types as string ...$expressions. Every invitation-existence check would be a TypeError.

This was found in phpstan-baseline.neon rather than in the source, and the entry states the defect outright:

message: '#^Parameter \#1 \$select of method Doctrine\\DBAL\\Query\\QueryBuilder\:\:select\(\) expects array\<string\>\|string\|null, int given\.$#'
path: src/lib/Invitation/Persistence/DoctrineGateway.php

Under DBAL 3 that was a type-hint violation that happened to work; under DBAL 4 it is a hard failure. The entry is removed rather than regenerated.

Nothing else here needs porting. lastInsertId() is used once, on ibexa_user_invitations, which is SERIAL/auto-increment, so DBAL 4's NoIdentityValue does not apply.

For QA:

Inviting a user, and inviting an address that has already been invited — the second is the path through the changed query.

Documentation:

N/A

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud