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

A larger set of functions should cause the result of a SELECT not to be cached.

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 23.02, 23.08, 24.02, 25.01, 25.10
    • 25.10.4
    • cache
    • None

    Description

      With selects=verify_cacheable, the cache will not store the resultsets of SELECTs that use functions or fields that are not cacheable; e.g. CURRENT_TIME(). However, it does not detect all functions that could be detected.

      A workaround is to create an unlike rule that causes SELECTs that use a particular function not to be cached.

      Futher, the cache should also not cache the result of SELECT ... FOR UPDATE and SELECT ... LOCK IN SHARE MODE.

      Attachments

        Activity

          People

            johan.wikman Johan Wikman
            johan.wikman Johan Wikman
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0d
                0d
                Logged:
                Time Spent - 1h
                1h

                Git Integration

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