[
https://issues.apache.org/jira/browse/JDO-734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14512926#comment-14512926
]
Andy Jefferson commented on JDO-734:
------------------------------------
Each application, in general, would have its own PMF, so they wouldn't be using
the same namespace.
If two applications were using the same namespace then, if we think this is a
problem, we ought to address the same concern on dynamic metadata creation and
dynamic fetch groups.
> Ability to save a (created) query as a named query for later use
> ----------------------------------------------------------------
>
> Key: JDO-734
> URL: https://issues.apache.org/jira/browse/JDO-734
> Project: JDO
> Issue Type: New Feature
> Components: api, specification, tck
> Reporter: Andy Jefferson
> Fix For: JDO 3.2
>
> Attachments: JDO-734.api.patch
>
>
> When a user goes to the trouble of creating a query to retrieve some
> information it is a common enough scenario that this will need to be
> performed again during the application lifetime. Being able to save a query
> (once created) as a named query (in the PMF) would mean that applications can
> skip the generation step off for subsequent runs.
> Suggested API change would be to add a single method to Query.
> Query q = pm1.newQuery("SELECT p FROM Person p WHERE firstName == :param");
> q.saveAsNamedQuery("PeopleWithName");
> q.execute("John");
> ... (some time later)
> Query q = pm2.newNamedQuery(Person.class, "PeopleWithName");
> q.execute("Brian");
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
