Uploaded image for project: 'Cayenne'
  1. Cayenne
  2. CAY-1127

Stop using query NAME as a cache key

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 3.0
    • 3.0M5
    • Core Library
    • None

    Description

      In 3.0 Cayenne can automatically build cache keys for all major queries, still we are supporting a legacy mechanism for using query names as cache keys. This is counterintuitive and actually resulted in some bugs in the user code (caused by cache keys from two distinct queries obtained by cloning the same mapped query, overriding each other, so the users are presented with inconsistent results).

      So I am going to remove the old behavior. Query name will no longer be used as a cache key.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            andrus Andrus Adamchik
            andrus Andrus Adamchik
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment