[ http://jira.jboss.com/jira/browse/JBSEAM-3032?page=all ] Dan Allen updated JBSEAM-3032: ------------------------------ Summary: count query used by Query is not compliant JPQL (was: count query used by EntityHome is not compliant JPQL) Description: The count query used by getCountEjbQl() in Query is not compliant JPQL. It should be: select count(Entity) from Entity entity instead of select count(*) from Entity entity Where "entity" is the class name of the entity (for instance, Person). You can test this by using TopLink or OpenJPA. All we need to do is replace the * with the name of the Entity. (We don't even need to fish for the alias used in the query). was: The count query used by getCountEjbQl() in EntityHome is not compliant JPQL. It should be: select count(Entity) from Entity entity instead of select count(*) from Entity entity Where "entity" is the class name of the entity (for instance, Person). You can test this by using TopLink or OpenJPA. All we need to do is replace the * with the name of the Entity. (We don't even need to fish for the alias used in the query). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-3032?page=all ] Dan Allen updated JBSEAM-3032: ------------------------------ Attachment: JBSEAM-3032-trunk-v1.txt -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3032?page=com.atlassian.jira.pl... ] Mathias Walter commented on JBSEAM-3032: ---------------------------------------- When get's it merged with the trunk? Is there a way to override it in general so it can be used for all queries in components.xml? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3032?page=com.atlassian.jira.pl... ] Dan Allen commented on JBSEAM-3032: ----------------------------------- This issue depends on a Hibernate issue. http://opensource.atlassian.com/projects/hibernate/browse/HHH-2266 Hibernate can support either of the following: select count(u) from User u select count(*) from User u as long as the primary key is a single field. However, when the primary key is a composite key, then Hibernate generates invalid SQL for the following: select count(v) from Vehicle v select count((vehicle0_.registration, vehicle0_.state)) as col_0_0_ from Vehicle vehicle0_ So we can't move forward until Hibernate is fixed and upgrade in JBoss AS 5. We will have to detect the Hibernate version too because we don't want to break things. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3032?page=com.atlassian.jira.pl... ] Dan Allen resolved JBSEAM-3032. ------------------------------- Fix Version/s: 2.2.0.CR1 (was: The future) Resolution: Done I detect whether Hibernate is the JPA provider in the @Create method. That sets a flag as to whether to use the compliant subject for the count query or not. By default, the subject is *. If Hibernate is not the provider, the subject becomes the match group in the select clause. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3032?page=com.atlassian.jira.pl... ] Pete Muir reopened JBSEAM-3032: ------------------------------- You should use PersistenceProvider for this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3032?page=com.atlassian.jira.pl... ] Pete Muir commented on JBSEAM-3032: ----------------------------------- exactly Agreed, but thats another discussion best left for Seam3. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3032?page=com.atlassian.jira.pl... ] Julien Kronegg commented on JBSEAM-3032: ---------------------------------------- Corresponding issue in OpenJPA: https://issues.apache.org/jira/browse/OPENJPA-566 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3032?page=com.atlassian.jira.pl... ] Pete Muir closed JBSEAM-3032. ----------------------------- -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira