샘플
Handle DBAL 4 transaction savepoint isolation, CompositeExpression immutability, and Result fetch indexing differences
sha256:92cf176cb7b66c578f8df42d44789e686a21fa578ec7cba999e0d8082036a74e
PUBLISHED
L3_CONTRACT_PASS
MIT-0
케이스
- 목표
- Handle DBAL 4 transaction savepoint isolation, CompositeExpression immutability, and Result fetch indexing differences HOW
- 패키지
- doctrine/dbal 4.4.4
- 환경
- php
- 생성일
- 2026-08-16T08:34:43Z
컨트랙트
- In DBAL 4 nested transactions always create SQL savepoints, so an inner rollBack() reverts only to the savepoint and does not mark the outer transaction rollback-only.
- Attempting to disable savepoints via setNestTransactionsWithSavepoints(false) throws InvalidArgumentException because nesting without savepoints was removed in DBAL 4.
- With autoCommit=false, executing queries starts a Level 1 transaction, a manual beginTransaction() increments to Level 2 (savepoint), and commit() immediately restarts Level 1 so the nesting level never drops to 0.
- Calling commit() with autoCommit=true and no active transaction throws Doctrine\DBAL\Exception\NoActiveTransaction.
- CompositeExpression is immutable: calling with() returns a new clone without mutating the caller in place, meaning unassigned calls silently drop filter conditions.
- Result::fetchAllAssociativeIndexed() keys the result by the first column and shifts that column out of the row dictionary values.
- Result::fetchAllKeyValue() requires at least two columns and silently ignores any columns beyond the first two.
파일
- NOTES.md
- composer.json
- composer.lock
- csx.json
- phpunit.xml
- tests/ContractTest.php
검증된 아티팩트 내려받기 (tar.gz) — 컨트랙트가 실제로 실행된 바로 그 바이트
오리진 시더
검증 영수증
- php 8 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · composer@1 · 2026-08-16 · ed25519:d91480838ac982c9