Uploaded image for project: 'CiviCRM'
  1. CiviCRM
  2. CRM-12341

prev/next cache should not do double-ended wildcard search

    Details

    • Type: Bug
    • Status: Done/Fixed
    • Priority: Minor
    • Resolution: Fixed/Completed
    • Affects Version/s: 4.2.8
    • Fix Version/s: 4.3.1
    • Component/s: Core CiviCRM
    • Labels:

      Description

      The civicrm_prev_next_cache is searched using the following condition:
      WHERE cacheKey LIKE '%civicrm search 8d293ba30d24366769b0d6d62285aafe_2168%

      If there is a prefix added to the key, that should be refactored into a separate key "domain" or whatever the prefix contains, so that we only need the wildcard at the end.

        Attachments

          Activity

            People

            • Assignee:
              lobo Donald A. Lobo
              Reporter:
              adamw Adam Wight
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: