You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cayenne.apache.org by "Nikita Timofeev (JIRA)" <ji...@apache.org> on 2017/02/10 15:28:41 UTC

[jira] [Closed] (CAY-2224) Make SelectQueryMetadata cache key generation aware of SelectQuery columns and name

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

Nikita Timofeev closed CAY-2224.
--------------------------------
    Resolution: Fixed

Fixed per https://github.com/apache/cayenne/commit/274d192be3227ea4c0017612c64ef2cd98d02665

> Make SelectQueryMetadata cache key generation aware of SelectQuery columns and name
> -----------------------------------------------------------------------------------
>
>                 Key: CAY-2224
>                 URL: https://issues.apache.org/jira/browse/CAY-2224
>             Project: Cayenne
>          Issue Type: Bug
>          Components: Core Library
>    Affects Versions: 4.0.M5
>            Reporter: Nikita Timofeev
>            Assignee: Nikita Timofeev
>             Fix For: 4.0.M5
>
>
> First problem is that queries like {{ObjectSelect.query(Artist.class).select(..)}} and {{ObjectSelect.query(Artist.class).selectCount(..)}} have the same cache key.
> Another problem is that MapQueryCache can't distinguish cache entries when QueryMetadata differs only with cache groups. 
> So may be it is a good idea to use query name as part of cache key (if it is set).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)