Skip to content

feat: Connection::transaction_capable - #970

Merged
pacman82 merged 1 commit into
pacman82:mainfrom
alfhellmund:feat/transaction-capable
Nov 10, 2026
Merged

pacman82 merged 1 commit into
pacman82:mainfrom
alfhellmund:feat/transaction-capable

Conversation

@alfhellmund

Copy link
Copy Markdown
Contributor

Follow-up to #960, as announced there: adds Connection::transaction_capable(), which reads SQL_TXN_CAPABLE via SQLGetInfo and returns odbc_sys::TransactionCapable directly (pacman82/odbc-sys#112). The minimum odbc-sys version is raised to 0.31.3, the release that introduced the type.

The integration test checks the expected value per database as a second test-case argument: ALL for Microsoft SQL Server, SQLite 3 and PostgreSQL, DDL_COMMIT for MariaDB.

I ran the integration tests locally in the test_linux container from docker-compose-ci.yml. All four transaction_capable cases pass. The only failures were two DuckDB tests: the image downloads the linux-amd64 DuckDB driver, which cannot load on my arm64 machine. That has nothing to do with this change.

One note on the release PR #969: the 30.1.0 changelog entry takes its heading from the squashed commit of #960, Connection::is_autocommit and Connection::transaction_capable. That commit only contains is_autocommit, so if 30.1.0 ships before this PR, the heading names a method the release does not have.

🤖 Generated with Claude Code

`transaction_capable()` reads `SQL_TXN_CAPABLE` via `SQLGetInfo` and
returns `odbc_sys::TransactionCapable`. Requires odbc-sys 0.31.3, which
introduced the type.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@pacman82
pacman82 merged commit 2f720d9 into pacman82:main Nov 10, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants