[MXS-6886] SQL_MODE tracked by MaxScale is not reset on COM_CHANGE_USER/COM_RESET_CONNECTION - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 23.02.18, 23.08.14, 24.02.10, 25.01.7, 25.10.3
Fix Version/s: 23.02.19, 23.08.15, 24.02.11, 25.01.8, 25.10.4
Component/s: Protocol
Labels:
None

Description

The SQL_MODE that MaxScale assumes is active has a minor effect on some of the SQL parsing. The tracked value in MaxScale is not reset when the client executes a COM_CHANGE_USER or COM_RESET_CONNECTION which causes the previously active mode to be left on even when it should be reset.

Attachments

Activity

People

Assignee:: markus makela

Reporter:: markus makela

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Dates

Created:: 2026-08-28 10:16

Updated:: 2026-09-01 07:11

Resolved:: 2026-09-01 07:11

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.