From: sergiyvamz (@sergiyvamz) <noreply+sergiyvamz@github.com>
To: aws/aws-advanced-jdbc-wrapper <noreply+aws-aws-advanced-jdbc-wrapper@github.com>
Subject: Re: [aws/aws-advanced-jdbc-wrapper] PR #2215: fix: check target driver for current transaction state
Date: Thu, 12 Nov 2026 17:53:11 +0000
Message-ID: <gh-aws-aws-advanced-jdbc-wrapper-2215-c6831531218@github.com> (raw)
In-Reply-To: <gh-aws-aws-advanced-jdbc-wrapper-2215@github.com>
References: <gh-aws-aws-advanced-jdbc-wrapper-2215@github.com>
Follow-up in 444348b4: the MariaDB driver exposes the same flag (`ServerStatus.IN_TRANSACTION` on the connection context), so `MariadbTargetDriverDialect` reports it now too. With that, `DefaultConnectionPlugin` skips the SQL analysis for transaction boundaries whenever the dialect reports state for the current connection; it only still looks for `SET AUTOCOMMIT` so the driver's autocommit view stays in step. The tracked-state fallback is unchanged and is now exercised by forcing the generic dialect in `TransactionStateTests`, and per transition in `DefaultConnectionPluginTest`.