[MXS-3850] MaxScale misinterprets SET GLOBAL autocommit=0 Created: 2021-11-03 Updated: 2021-11-13 Resolved: 2021-11-11 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Protocol, qc_sqlite |
| Affects Version/s: | 2.5.16 |
| Fix Version/s: | 22.08.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | markus makela | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Sprint: | MXS-SPRINT-144 |
| Description |
|
When a user executes a SET GLOBAL autocommit=0 statement, the autocommit state for all new connections is changed. The autocommit state remains the same for the current connection. MaxScale treats this as if it were a SET SESSION autocommit=0 statement. |