fix: cast Postgre batch subquery values so updateBatch() and deleteBatch() accept mixed PHP types

[paulbalandan]

Description
Fixes #10599

Checklist:

• Securely signed commits
• Component(s) with PHPDoc blocks, only if necessary or adds value (without duplication)
• Unit testing, with >80% coverage
• User guide updated
• Conforms to style guide

[Copilot]

Copilot review overview

🟡 Changes recommended

Mapped or qualified columns can remain uncast, while enum, domain, and array metadata can generate invalid PostgreSQL casts.

Review effort: Balanced
Findings: 1 · 2

Open (3)

• Resolve mapped source keys before determining field types · New
• Handle PostgreSQL enum, domain, and array metadata types · New
• Support qualified mapped constraint columns · New

What changed in this PR

Fixes PostgreSQL batch updates/deletes with mixed PHP value types by casting subquery values to target column types.

Changes:

• Adds PostgreSQL value casting for batch operations.
• Adds live database regression tests.
• Documents the fix in the 4.7.5 changelog.

Base branch assumed to be develop. Static review performed; database validation remains with GitHub Actions.

File	Description
system/​Database/​Postgre/​Builder.php	Casts PostgreSQL batch subquery values.
tests/​system/​Database/​Live/​UpdateTest.php	Tests mixed-type batch updates.
tests/​system/​Database/​Live/​DeleteTest.php	Tests mixed-type batch deletes.
user_guide_src/​source/​changelogs/​v4.7.5.rst	Records the bug fix.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[michalsn]

Casting delete constraint values to CHAR(n) can change which rows match. For example, with a CHAR(3) column, 'ABCD' is truncated to 'ABC', so deleteBatch() can delete the row containing 'ABC' even though the supplied value does not match it. The comparison should preserve the full input value.

[paulbalandan]

Casting delete constraint values to CHAR(n) can change which rows match. For example, with a CHAR(3) column, 'ABCD' is truncated to 'ABC', so deleteBatch() can delete the row containing 'ABC' even though the supplied value does not match it. The comparison should preserve the full input value.

Fixed. The casting now uses BPCHAR whenever CHAR(n) was used.

[paulbalandan]

Thank you, @michalsn , for the reviews!