openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Helen Xu (JIRA)" <j...@apache.org>
Subject [jira] [Created] (OPENJPA-2295) speed up query metadata lookup
Date Thu, 08 Nov 2012 17:12:13 GMT
Helen Xu created OPENJPA-2295:
---------------------------------

             Summary: speed up query metadata lookup
                 Key: OPENJPA-2295
                 URL: https://issues.apache.org/jira/browse/OPENJPA-2295
             Project: OpenJPA
          Issue Type: Bug
          Components: performance, query
            Reporter: Helen Xu
            Assignee: Helen Xu
            Priority: Minor


I noticed that it used the queryKey as the map key for metadataRepository._queries, but when
it goes to look up, it always uses query name. 

I double checked the JPA Spec and OPENJPA menu, it seems only support the named query creation
using query name, which means the query name should be unique in one EntityManager. It doesn't
matter in which entity the query is defined. So using name as the map look up key should be
good enough.

when there are two queries with the same name defined in the different entities, it will only
keep the query metadata for the first loaded named query and ignore the rest plus log a warning
message like this:
 WARN   [main] openjpa.MetaData - Ignoring duplicate query "X" in "class org.apache.openjpa.A".
A query with the same name been already declared in "class org.apache.openjpa.B".

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message