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

"transaction" is always parsed as a reserved word

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.5, 6
    • Fix Version/s: 2.5.19, 6.2.2
    • Component/s: qc_sqlite
    • Labels:
      None

      Description

      MaxScale always parses "transaction" as a reserved word. The implication is that e.g. the parsing of the statement

      SELECT uuid FROM Transaction LIMIT 1
      

      fails and the statement is classified only based upon the SELECT keyword. That works fine except when the firewall or the masking filters are used as they reject statements that cannot be fully parsed.

        Attachments

          Activity

            People

            Assignee:
            johan.wikman Johan Wikman
            Reporter:
            johan.wikman Johan Wikman
            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.