v0.28.19
0.28.19
Changed 1
- Controlled PostgreSQL transactions whose commit is turned into a rollback are marked as rolled back and release their connection, and a subsequent rollback().execute() succeeds without sending another rollback
Fixed 2
- PostgreSQL clients whose rollback fails are discarded instead of being returned to the pool for reuse
- PostgreSQL commits that are turned into rollbacks now throw AbortedTransactionError instead of reporting success behavior changed · inferred, marked in the notes below
1 change to check, marked in the notes below
From Kysely
Hey 👋
A small batch of bug fixes. Please report any issues. 🤞😰🤞
This maintenance release backports the PostgreSQL transaction fixes from 0.29.8.
PostgreSQL transactions get two fixes:
- Clients whose rollback fails are discarded instead of returned to the pool for reuse.
- Commits that PostgreSQL turns into rollbacks now throw
AbortedTransactionErrorinstead of reporting success. Controlled transactions are marked as rolled back and release their connection; a subsequentrollback().execute()safely succeeds without sending another rollback. behavior changed · inferred
🚀 Features
🐞 Bugfixes
PostgreSQL 🐘
- fix(postgres): discard clients after failed rollbacks by @igalklebanov in https://github.com/kysely-org/kysely/pull/2155
- fix(postgres): reject commits that roll back aborted transactions by @igalklebanov in https://github.com/kysely-org/kysely/pull/2161
📖 Documentation
📦 CICD & Tooling
⚠️ Breaking Changes
🐤 New Contributors
What's Changed
Full Changelog: https://github.com/kysely-org/kysely/compare/v0.28.18...v0.28.19