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

qc_sqlite handles current_timestamp etc. explicitly

    XMLWordPrintable

    Details

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

      Description

      The sqlite3 tokenizer detects current_timestamp, current_time and current_date explicitly and returns a specific token for them. That means that if current_timestamp() is used, it will cause a parser error. That specific handling should simply be removed as that means that they will be handled like all other variables and functions are handled.

        Attachments

          Issue Links

            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