Releases: Dorpmaster/dbal-amphp-postgres
Releases · Dorpmaster/dbal-amphp-postgres
Release list
1.2.0
Added
- Added a bundled Composer Patches workflow for
amphp/postgres, includingpatches.json,patches.lock.json, and release-managed patch artifacts. - Added regression coverage for duplicate PostgreSQL aliases and Doctrine metadata introspection on the AMPHP-backed DBAL connection.
- Added public
getColumnName()support to the driver result layer through the patched upstream result API.
Fixed
- Fixed the transport contract to
ext-pgsqland removedext-pqfrom the supported driver surface. - Kept a normal Composer semver constraint for
amphp/postgres; the bundled compatibility patch is applied automatically and fails fast if upstream changes become incompatible. - Preserved positional row access for PostgreSQL results with duplicate aliases so DBAL
fetchNumeric()semantics remain intact. - Preserved ordered column names and associative semantics required by Doctrine's PostgreSQL schema introspection and migrations paths.
- Removed the AMPHP metadata incompatibility behind Doctrine errors such as
Undefined array key 10during PostgreSQL schema operations.
Documentation
- Documented the Composer plugin requirement for the bundled
amphp/postgrescompatibility patch. - Documented Doctrine Migrations support, duplicate alias behavior, and the
getColumnName()compatibility surface.
1.0.1
Release 1.0.1
Highlights
This release focuses on compatibility and release-readiness fixes after the initial 1.0.0 line: DBAL quoting support, safer typed parameter compatibility, verified DSN escaping behavior, and documentation cleanup.
Fixed
- DBAL compatibility: implemented
AmpPgConnection::quote() - Parameter conversion compatibility: typed
INTEGERandBOOLEANparameters now accept safe canonical string forms for DBAL compatibility - Ambiguous parameter values are still rejected explicitly, and PHP loose casting is still not used
DsnBuilderescaping behavior verified with live integration coverage against the AMPHP PostgreSQL connection-string parser- Documentation and release history aligned with the actual shipped behavior and limitations
Compatibility
Runtime and dependency requirements are unchanged relative to 1.0.0.
This release contains backward-compatible DBAL compatibility improvements.
Upgrade notes
No upgrade actions required.