You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@cayenne.apache.org by "Andrus Adamchik (JIRA)" <de...@cayenne.apache.org> on 2008/10/17 15:01:11 UTC

[jira] Created: (CAY-1127) Stop using query NAME as a cache key

Stop using query NAME as a cache key
------------------------------------

                 Key: CAY-1127
                 URL: https://issues.apache.org/cayenne/browse/CAY-1127
             Project: Cayenne
          Issue Type: Task
          Components: Cayenne Core Library
    Affects Versions: 3.0
            Reporter: Andrus Adamchik
            Assignee: Andrus Adamchik
             Fix For: 3.0


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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (CAY-1127) Stop using query NAME as a cache key

Posted by "Andrus Adamchik (JIRA)" <de...@cayenne.apache.org>.

     [ https://issues.apache.org/cayenne/browse/CAY-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrus Adamchik closed CAY-1127.
--------------------------------

    Resolution: Fixed

> Stop using query NAME as a cache key
> ------------------------------------
>
>                 Key: CAY-1127
>                 URL: https://issues.apache.org/cayenne/browse/CAY-1127
>             Project: Cayenne
>          Issue Type: Task
>          Components: Cayenne Core Library
>    Affects Versions: 3.0
>            Reporter: Andrus Adamchik
>            Assignee: Andrus Adamchik
>             Fix For: 3.0
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.