You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cayenne.apache.org by "Andrus Adamchik (JIRA)" <ji...@apache.org> on 2010/01/25 14:37:34 UTC
[jira] Created: (CAY-1374) Store queries in the DataMap using an
intermediate QueryHolder
Store queries in the DataMap using an intermediate QueryHolder
--------------------------------------------------------------
Key: CAY-1374
URL: https://issues.apache.org/jira/browse/CAY-1374
Project: Cayenne
Issue Type: Task
Components: Core Library
Affects Versions: 3.1M1
Reporter: Andrus Adamchik
Assignee: Olga Tkacheva
Fix For: 3.1M1
Mapped Queries are different from normal Cayenne project mapping objects (like say entities), as they can exist on their own, outside of a DataMap. Past attempts to make them look like mapped objects resulted in "getName()" method addtion to the query interface - a method that has little meaning for a query itself (especially since 3.0 when we stopped using "name" as a cache key).
Now per CAY-1339 we are getting rid of ProjectPath notion, and will assume that we can recreate a tree path just by looking at a given object (ConfigurationNode). So we'll need to add a method "getDataMap" to a query, which is another nonsense method for a generic query.
So instead we'll just add a o.a.c.map.QueryHolder object that will have name, dataMap and query properties, and that can be easily manipulated in the Modeler. Query.getName() should be deprecated and I guess that Query implementation of ConfigurationNode should be moved to QueryHolder.
This change should be mostly invisible to the end user.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (CAY-1374) Add parent dataMap property to Query
interface
Posted by "Olga Tkacheva (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAY-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olga Tkacheva closed CAY-1374.
------------------------------
Resolution: Fixed
> Add parent dataMap property to Query interface
> ----------------------------------------------
>
> Key: CAY-1374
> URL: https://issues.apache.org/jira/browse/CAY-1374
> Project: Cayenne
> Issue Type: Task
> Components: Core Library
> Affects Versions: 3.1M1
> Reporter: Andrus Adamchik
> Assignee: Olga Tkacheva
> Fix For: 3.1M1
>
>
> Add parent dataMap property to Query interface so that we can determine map paths for mapped queries. The solution is not ideal, as not all queries are mapped. As 3.1 progresses we may change that and instead use a special descriptor for each mapped query, and remove "dataMap" (and "name"!) properties from the Query interface.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAY-1374) Add parent dataMap property to Query
interface
Posted by "Andrus Adamchik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAY-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrus Adamchik updated CAY-1374:
---------------------------------
Description:
Add parent dataMap property to Query interface so that we can determine map paths for mapped queries. The solution is not ideal, as not all queries are mapped. As 3.1 progresses we may change that and instead use a special descriptor for each mapped query, and remove "dataMap" (and "name"!) properties from the Query interface.
was:
Mapped Queries are different from normal Cayenne project mapping objects (like say entities), as they can exist on their own, outside of a DataMap. Past attempts to make them look like mapped objects resulted in "getName()" method addtion to the query interface - a method that has little meaning for a query itself (especially since 3.0 when we stopped using "name" as a cache key).
Now per CAY-1339 we are getting rid of ProjectPath notion, and will assume that we can recreate a tree path just by looking at a given object (ConfigurationNode). So we'll need to add a method "getDataMap" to a query, which is another nonsense method for a generic query.
So instead we'll just add a o.a.c.map.QueryHolder object that will have name, dataMap and query properties, and that can be easily manipulated in the Modeler. Query.getName() should be deprecated and I guess that Query implementation of ConfigurationNode should be moved to QueryHolder.
This change should be mostly invisible to the end user.
Summary: Add parent dataMap property to Query interface (was: Store queries in the DataMap using an intermediate QueryHolder)
> Add parent dataMap property to Query interface
> ----------------------------------------------
>
> Key: CAY-1374
> URL: https://issues.apache.org/jira/browse/CAY-1374
> Project: Cayenne
> Issue Type: Task
> Components: Core Library
> Affects Versions: 3.1M1
> Reporter: Andrus Adamchik
> Assignee: Olga Tkacheva
> Fix For: 3.1M1
>
>
> Add parent dataMap property to Query interface so that we can determine map paths for mapped queries. The solution is not ideal, as not all queries are mapped. As 3.1 progresses we may change that and instead use a special descriptor for each mapped query, and remove "dataMap" (and "name"!) properties from the Query interface.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.