[MXS-3769] SET TRANSACTION READ ONLY not detected Created: 2021-09-16  Updated: 2022-02-02  Resolved: 2021-11-10

Status: Closed
Project: MariaDB MaxScale
Component/s: qc_sqlite
Affects Version/s: 2.4.17, 2.5.15, 6.1.1
Fix Version/s: 22.08.0

Type: Bug Priority: Major
Reporter: markus makela Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MXS-3947 Read-only transaction behavior is not... Closed
relates to MXS-3980 readwritesplit not understanding SET ... Closed
Sprint: MXS-SPRINT-141, MXS-SPRINT-143, MXS-SPRINT-144

 Description   

MaxScale does not detect that a transaction is read-only if SET TRANSACTION READ ONLY is used instead of the explicit START TRANSACTION READ ONLY.
Generated at Thu Feb 08 04:23:49 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.