Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-3184

COM_STMT_EXECUTE with FOUND_ROWS not routed to previous target

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Fixed
    • 2.3.20, 2.4.12, 2.5.3
    • 6.0.0
    • QueryClassifier
    • None
    • MXS-SPRINT-119

    Description

      With MXS-3143 fixed, COM_QUERY packets will be routed to the server where the last command was executed. This does not cover COM_STMT_EXECUTE packets which means that a prepared statement with FOUND_ROWS will not be handled the same way a COM_QUERY packet with FOUND_ROWS is.

      The fix to this is to classify queries like this as a special type which should be routed to the previous target, if it is still available.

      Attachments

        Activity

          People

            markus makela markus makela
            markus makela markus makela
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

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