[Hibernate-JIRA] Created: (HHH-5419) COUNT operator with composite primary key and JPA 2.0 Criteria API produces bad sql
9:31 a.m.
COUNT operator with composite primary key and JPA 2.0 Criteria API produces bad sql
-----------------------------------------------------------------------------------
Key: HHH-5419
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5419
Project: Hibernate Core
Issue Type: Bug
Affects Versions: 3.6.0.Beta1, 3.5.4, 3.5.3, 3.5.2, 3.5.1
Environment: hibernate-entitymanager 3.6.0.Beta1, glassfish 3.0.1, linux ubuntu
10.04, MS SQL Server 2008
Reporter: Fabio Braga de Oliveira
Attachments: hibernate-count-bug.zip
Hibernate produces a invalid SQL if anyone use the count() operator with the JPA 2.0
Criteria API. Code:
CriteriaBuilder cb = getEntityManager().getCriteriaBuilder();
CriteriaQuery<Object[]> cq = cb.createQuery(Object[].class);
Root<EntityCompositePK> r = cq.from(EntityCompositePK.class);
cq.multiselect(cb.count(r));
assertEquals(0, ((Long)
(getEntityManager().createQuery(cq).getSingleResult())[0]).intValue());
I'm sending a little maven project which reproduces the bug.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:56 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-5419) COUNT operator with composite primary key and JPA 2.0 Criteria API produces bad sql
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5419?page=c...
]
Steve Ebersole updated HHH-5419:
--------------------------------
Priority: Minor (was: Major)
Out of curiosity what is the "bad SQL"?
COUNT operator with composite primary key and JPA 2.0 Criteria API
produces bad sql
-----------------------------------------------------------------------------------
Key: HHH-5419
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5419
Project: Hibernate Core
Issue Type: Bug
Affects Versions: 3.5.1, 3.5.2, 3.5.3, 3.5.4, 3.6.0.Beta1
Environment: hibernate-entitymanager 3.6.0.Beta1, glassfish 3.0.1, linux ubuntu
10.04, MS SQL Server 2008
Reporter: Fabio Braga de Oliveira
Priority: Minor
Attachments: hibernate-count-bug.zip
Hibernate produces a invalid SQL if anyone use the count() operator with the JPA 2.0
Criteria API. Code:
CriteriaBuilder cb = getEntityManager().getCriteriaBuilder();
CriteriaQuery<Object[]> cq = cb.createQuery(Object[].class);
Root<EntityCompositePK> r = cq.from(EntityCompositePK.class);
cq.multiselect(cb.count(r));
assertEquals(0, ((Long)
(getEntityManager().createQuery(cq).getSingleResult())[0]).intValue());
I'm sending a little maven project which reproduces the bug.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:09 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-5419) COUNT operator with composite primary key and JPA 2.0 Criteria API produces bad sql
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5419?page=c...
]
Anne Buit commented on HHH-5419:
--------------------------------
select count(generatedAlias0)
from ProjectActivity as generatedAlias0
Using org.hibernate.dialect.SQLServerDialect, this translates into:
select top 2 count((projectact0_.project_id, projectact0_.project_activity_id)) as
col_0_0_
from project_activity projectact0_
The entire composite primary key is used within the count() operator.
COUNT operator with composite primary key and JPA 2.0 Criteria API
produces bad sql
-----------------------------------------------------------------------------------
Key: HHH-5419
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5419
Project: Hibernate Core
Issue Type: Bug
Affects Versions: 3.5.1, 3.5.2, 3.5.3, 3.5.4, 3.6.0.Beta1
Environment: hibernate-entitymanager 3.6.0.Beta1, glassfish 3.0.1, linux ubuntu
10.04, MS SQL Server 2008
Reporter: Fabio Braga de Oliveira
Priority: Minor
Attachments: hibernate-count-bug.zip
Hibernate produces a invalid SQL if anyone use the count() operator with the JPA 2.0
Criteria API. Code:
CriteriaBuilder cb = getEntityManager().getCriteriaBuilder();
CriteriaQuery<Object[]> cq = cb.createQuery(Object[].class);
Root<EntityCompositePK> r = cq.from(EntityCompositePK.class);
cq.multiselect(cb.count(r));
assertEquals(0, ((Long)
(getEntityManager().createQuery(cq).getSingleResult())[0]).intValue());
I'm sending a little maven project which reproduces the bug.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:31 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-5419) COUNT operator with composite primary key and JPA 2.0 Criteria API produces bad sql
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5419?page=c...
]
Steve Ebersole updated HHH-5419:
--------------------------------
Suitable for new contributors: [Yes, likely]
Affects Version/s: (was: 3.5.3)
(was: 3.5.2)
(was: 3.5.1)
Fix Version/s: 4.0.0.next
Assignee: John Verhaeg
The problem here is that this is perfectly valid ANSI SQL. So you are saying that SQL
Server just does not support this syntax.
We already have some methods on Dialect for what forms of tuple (or row value constructor)
syntax the database supports in various usages. We'll have to take a look and see
what is there and how we can leverage that.
COUNT operator with composite primary key and JPA 2.0 Criteria API
produces bad sql
-----------------------------------------------------------------------------------
Key: HHH-5419
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5419
Project: Hibernate Core
Issue Type: Bug
Affects Versions: 3.5.4, 3.6.0.Beta1
Environment: hibernate-entitymanager 3.6.0.Beta1, glassfish 3.0.1, linux ubuntu
10.04, MS SQL Server 2008
Reporter: Fabio Braga de Oliveira
Assignee: John Verhaeg
Priority: Minor
Fix For: 4.0.0.next
Attachments: hibernate-count-bug.zip
Hibernate produces a invalid SQL if anyone use the count() operator with the JPA 2.0
Criteria API. Code:
CriteriaBuilder cb = getEntityManager().getCriteriaBuilder();
CriteriaQuery<Object[]> cq = cb.createQuery(Object[].class);
Root<EntityCompositePK> r = cq.from(EntityCompositePK.class);
cq.multiselect(cb.count(r));
assertEquals(0, ((Long)
(getEntityManager().createQuery(cq).getSingleResult())[0]).intValue());
I'm sending a little maven project which reproduces the bug.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:42 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-5419) COUNT operator with composite primary key and JPA 2.0 Criteria API produces bad sql
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5419?page=c...
]
Steve Ebersole updated HHH-5419:
--------------------------------
Fix Version/s: (was: 4.0.0.CR2)
4.0.0.next
COUNT operator with composite primary key and JPA 2.0 Criteria API
produces bad sql
-----------------------------------------------------------------------------------
Key: HHH-5419
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5419
Project: Hibernate Core
Issue Type: Bug
Affects Versions: 3.5.4, 3.6.0.Beta1
Environment: hibernate-entitymanager 3.6.0.Beta1, glassfish 3.0.1, linux ubuntu
10.04, MS SQL Server 2008
Reporter: Fabio Braga de Oliveira
Assignee: John Verhaeg
Priority: Minor
Fix For: 4.0.0.next
Attachments: hibernate-count-bug.zip
Hibernate produces a invalid SQL if anyone use the count() operator with the JPA 2.0
Criteria API. Code:
CriteriaBuilder cb = getEntityManager().getCriteriaBuilder();
CriteriaQuery<Object[]> cq = cb.createQuery(Object[].class);
Root<EntityCompositePK> r = cq.from(EntityCompositePK.class);
cq.multiselect(cb.count(r));
assertEquals(0, ((Long)
(getEntityManager().createQuery(cq).getSingleResult())[0]).intValue());
I'm sending a little maven project which reproduces the bug.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:09 a.m.
New subject: [Hibernate-JIRA] Issue Comment Edited: (HHH-5419) COUNT operator with composite primary key and JPA 2.0 Criteria API produces bad sql
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5419?page=c...
]
Oliver Gierke edited comment on HHH-5419 at 9/5/11 1:07 AM:
------------------------------------------------------------
The interesting part about is that a) the problem also exists for the use of JPQL, but can
be worked around by using {{count(*)}} in that case. So it seems that {{count(*)}} is
translated differently into SQL that a {{count(x)}}. Is there a reason to treat both
approaches differently?
Reading up the other tickets it seems the problem is not only related to a single dialect
but (almost) all available. Here's the complete list (derived from the other
tickets):
* Oracle
* MySQL
* HSQL
* MSSQL
was (Author: oliver.gierke):
The interesting part about is that a) the problem also exists for the use of JPQL, but
can be worked around by using {{count(*)}} in that case. So it seems that {{count(*)}} is
translated differently into SQL that a {{count(x)}}. Is there a reason to treat both
approaches differently?
COUNT operator with composite primary key and JPA 2.0 Criteria API
produces bad sql
-----------------------------------------------------------------------------------
Key: HHH-5419
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5419
Project: Hibernate Core
Issue Type: Bug
Affects Versions: 3.5.4, 3.6.0.Beta1
Environment: hibernate-entitymanager 3.6.0.Beta1, glassfish 3.0.1, linux ubuntu
10.04, MS SQL Server 2008
Reporter: Fabio Braga de Oliveira
Assignee: John Verhaeg
Priority: Minor
Fix For: 4.0.0.next
Attachments: hibernate-count-bug.zip
Hibernate produces a invalid SQL if anyone use the count() operator with the JPA 2.0
Criteria API. Code:
CriteriaBuilder cb = getEntityManager().getCriteriaBuilder();
CriteriaQuery<Object[]> cq = cb.createQuery(Object[].class);
Root<EntityCompositePK> r = cq.from(EntityCompositePK.class);
cq.multiselect(cb.count(r));
assertEquals(0, ((Long)
(getEntityManager().createQuery(cq).getSingleResult())[0]).intValue());
I'm sending a little maven project which reproduces the bug.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:35 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-5419) COUNT operator with composite primary key and JPA 2.0 Criteria API produces bad sql
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5419?page=c...
]
John Verhaeg updated HHH-5419:
------------------------------
Affects Version/s: 4.0.0.CR3
COUNT operator with composite primary key and JPA 2.0 Criteria API
produces bad sql
-----------------------------------------------------------------------------------
Key: HHH-5419
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5419
Project: Hibernate Core
Issue Type: Bug
Affects Versions: 3.5.4, 3.6.0.Beta1, 4.0.0.CR3
Environment: hibernate-entitymanager 3.6.0.Beta1, glassfish 3.0.1, linux ubuntu
10.04, MS SQL Server 2008
Reporter: Fabio Braga de Oliveira
Assignee: John Verhaeg
Priority: Minor
Fix For: 4.0.0.next
Attachments: hibernate-count-bug.zip
Hibernate produces a invalid SQL if anyone use the count() operator with the JPA 2.0
Criteria API. Code:
CriteriaBuilder cb = getEntityManager().getCriteriaBuilder();
CriteriaQuery<Object[]> cq = cb.createQuery(Object[].class);
Root<EntityCompositePK> r = cq.from(EntityCompositePK.class);
cq.multiselect(cb.count(r));
assertEquals(0, ((Long)
(getEntityManager().createQuery(cq).getSingleResult())[0]).intValue());
I'm sending a little maven project which reproduces the bug.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:02 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-5419) COUNT operator with composite primary key and JPA 2.0 Criteria API produces bad sql
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5419?page=c...
]
Steve Ebersole updated HHH-5419:
--------------------------------
Fix Version/s: (was: 4.0.0.CR4)
4.0.0.next
COUNT operator with composite primary key and JPA 2.0 Criteria API
produces bad sql
-----------------------------------------------------------------------------------
Key: HHH-5419
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5419
Project: Hibernate Core
Issue Type: Bug
Affects Versions: 3.5.4, 3.6.0.Beta1, 4.0.0.CR3
Environment: hibernate-entitymanager 3.6.0.Beta1, glassfish 3.0.1, linux ubuntu
10.04, MS SQL Server 2008
Reporter: Fabio Braga de Oliveira
Assignee: John Verhaeg
Priority: Minor
Fix For: 4.0.0.next
Attachments: hibernate-count-bug.zip
Hibernate produces a invalid SQL if anyone use the count() operator with the JPA 2.0
Criteria API. Code:
CriteriaBuilder cb = getEntityManager().getCriteriaBuilder();
CriteriaQuery<Object[]> cq = cb.createQuery(Object[].class);
Root<EntityCompositePK> r = cq.from(EntityCompositePK.class);
cq.multiselect(cb.count(r));
assertEquals(0, ((Long)
(getEntityManager().createQuery(cq).getSingleResult())[0]).intValue());
I'm sending a little maven project which reproduces the bug.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:49 p.m.
New subject: [Hibernate-JIRA] Resolved: (HHH-5419) COUNT operator with composite primary key and JPA 2.0 Criteria API produces bad sql
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5419?page=c...
]
John Verhaeg resolved HHH-5419.
-------------------------------
Resolution: Fixed
Fix Version/s: 4.0.0.CR4
Modified HQL rendering of COUNT function so that when a non-distinct entity with an ID is
specified as a parameter, it renders a star instead of the ID attribute(s). This allows
for greater support across DBs, since some do not support the previous rendering of
multiple ID attributes when the ID happens to be a composite ID.
COUNT operator with composite primary key and JPA 2.0 Criteria API
produces bad sql
-----------------------------------------------------------------------------------
Key: HHH-5419
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5419
Project: Hibernate Core
Issue Type: Bug
Affects Versions: 3.5.4, 3.6.0.Beta1, 4.0.0.CR3
Environment: hibernate-entitymanager 3.6.0.Beta1, glassfish 3.0.1, linux ubuntu
10.04, MS SQL Server 2008
Reporter: Fabio Braga de Oliveira
Assignee: John Verhaeg
Priority: Minor
Fix For: 4.0.0.next, 4.0.0.CR4
Attachments: hibernate-count-bug.zip
Hibernate produces a invalid SQL if anyone use the count() operator with the JPA 2.0
Criteria API. Code:
CriteriaBuilder cb = getEntityManager().getCriteriaBuilder();
CriteriaQuery<Object[]> cq = cb.createQuery(Object[].class);
Root<EntityCompositePK> r = cq.from(EntityCompositePK.class);
cq.multiselect(cb.count(r));
assertEquals(0, ((Long)
(getEntityManager().createQuery(cq).getSingleResult())[0]).intValue());
I'm sending a little maven project which reproduces the bug.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:59 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-5419) COUNT operator with composite primary key and JPA 2.0 Criteria API produces bad sql
[
https://hibernate.onjira.com/browse/HHH-5419?page=com.atlassian.jira.plug...
]
Jeremy Whiting commented on HHH-5419:
-------------------------------------
This issue is happening on MariaDB. Seeing it is a MySQL derivative should this not be
working with MariaDB too ?
COUNT operator with composite primary key and JPA 2.0 Criteria API
produces bad sql
-----------------------------------------------------------------------------------
Key: HHH-5419
URL: https://hibernate.onjira.com/browse/HHH-5419
Project: Hibernate ORM
Issue Type: Bug
Affects Versions: 3.5.4, 3.6.0.Beta1, 4.0.0.CR3
Environment: hibernate-entitymanager 3.6.0.Beta1, glassfish 3.0.1, linux ubuntu
10.04, MS SQL Server 2008
Reporter: Fabio Braga de Oliveira
Assignee: John Verhaeg
Priority: Minor
Fix For: 4.0.0.CR4, 4.0.0.CR5
Attachments: hibernate-count-bug.zip
Hibernate produces a invalid SQL if anyone use the count() operator with the JPA 2.0
Criteria API. Code:
CriteriaBuilder cb = getEntityManager().getCriteriaBuilder();
CriteriaQuery<Object[]> cq = cb.createQuery(Object[].class);
Root<EntityCompositePK> r = cq.from(EntityCompositePK.class);
cq.multiselect(cb.count(r));
assertEquals(0, ((Long)
(getEntityManager().createQuery(cq).getSingleResult())[0]).intValue());
I'm sending a little maven project which reproduces the bug.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:38 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-5419) COUNT operator with composite primary key and JPA 2.0 Criteria API produces bad sql
[
https://hibernate.onjira.com/browse/HHH-5419?page=com.atlassian.jira.plug...
]
Gail Badner commented on HHH-5419:
----------------------------------
This issue has been fixed. If you are still seeing your issue using 4.1.1 (due out today),
then please open a new issue and provide a test case that reproduces your issue.
COUNT operator with composite primary key and JPA 2.0 Criteria API
produces bad sql
-----------------------------------------------------------------------------------
Key: HHH-5419
URL: https://hibernate.onjira.com/browse/HHH-5419
Project: Hibernate ORM
Issue Type: Bug
Affects Versions: 3.5.4, 3.6.0.Beta1, 4.0.0.CR3
Environment: hibernate-entitymanager 3.6.0.Beta1, glassfish 3.0.1, linux ubuntu
10.04, MS SQL Server 2008
Reporter: Fabio Braga de Oliveira
Assignee: John Verhaeg
Priority: Minor
Fix For: 4.0.0.CR4, 4.0.0.CR5
Attachments: hibernate-count-bug.zip
Hibernate produces a invalid SQL if anyone use the count() operator with the JPA 2.0
Criteria API. Code:
CriteriaBuilder cb = getEntityManager().getCriteriaBuilder();
CriteriaQuery<Object[]> cq = cb.createQuery(Object[].class);
Root<EntityCompositePK> r = cq.from(EntityCompositePK.class);
cq.multiselect(cb.count(r));
assertEquals(0, ((Long)
(getEntityManager().createQuery(cq).getSingleResult())[0]).intValue());
I'm sending a little maven project which reproduces the bug.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:18 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-5419) COUNT operator with composite primary key and JPA 2.0 Criteria API produces bad sql
[
https://hibernate.onjira.com/browse/HHH-5419?page=com.atlassian.jira.plug...
]
Jeremy Whiting commented on HHH-5419:
-------------------------------------
I am using AS7.1 and still seeing this. I will raise it there so that the version bundled
in as7 will eventually pull in the version of Hibernate with the fix for MariaDB.
COUNT operator with composite primary key and JPA 2.0 Criteria API
produces bad sql
-----------------------------------------------------------------------------------
Key: HHH-5419
URL: https://hibernate.onjira.com/browse/HHH-5419
Project: Hibernate ORM
Issue Type: Bug
Affects Versions: 3.5.4, 3.6.0.Beta1, 4.0.0.CR3
Environment: hibernate-entitymanager 3.6.0.Beta1, glassfish 3.0.1, linux ubuntu
10.04, MS SQL Server 2008
Reporter: Fabio Braga de Oliveira
Assignee: John Verhaeg
Priority: Minor
Fix For: 4.0.0.CR4, 4.0.0.CR5
Attachments: hibernate-count-bug.zip
Hibernate produces a invalid SQL if anyone use the count() operator with the JPA 2.0
Criteria API. Code:
CriteriaBuilder cb = getEntityManager().getCriteriaBuilder();
CriteriaQuery<Object[]> cq = cb.createQuery(Object[].class);
Root<EntityCompositePK> r = cq.from(EntityCompositePK.class);
cq.multiselect(cb.count(r));
assertEquals(0, ((Long)
(getEntityManager().createQuery(cq).getSingleResult())[0]).intValue());
I'm sending a little maven project which reproduces the bug.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:09 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-5419) COUNT operator with composite primary key and JPA 2.0 Criteria API produces bad sql
[
https://hibernate.onjira.com/browse/HHH-5419?page=com.atlassian.jira.plug...
]
Steve Ebersole commented on HHH-5419:
-------------------------------------
Well we still need to make sure it works for you with your db in SOME release of
Hibernate. Otherwise JBoss has nothing to pull in. What Dialect do you use?
COUNT operator with composite primary key and JPA 2.0 Criteria API
produces bad sql
-----------------------------------------------------------------------------------
Key: HHH-5419
URL: https://hibernate.onjira.com/browse/HHH-5419
Project: Hibernate ORM
Issue Type: Bug
Affects Versions: 3.5.4, 3.6.0.Beta1, 4.0.0.CR3
Environment: hibernate-entitymanager 3.6.0.Beta1, glassfish 3.0.1, linux ubuntu
10.04, MS SQL Server 2008
Reporter: Fabio Braga de Oliveira
Assignee: John Verhaeg
Priority: Minor
Fix For: 4.0.0.CR4, 4.0.0.CR5
Attachments: hibernate-count-bug.zip
Hibernate produces a invalid SQL if anyone use the count() operator with the JPA 2.0
Criteria API. Code:
CriteriaBuilder cb = getEntityManager().getCriteriaBuilder();
CriteriaQuery<Object[]> cq = cb.createQuery(Object[].class);
Root<EntityCompositePK> r = cq.from(EntityCompositePK.class);
cq.multiselect(cb.count(r));
assertEquals(0, ((Long)
(getEntityManager().createQuery(cq).getSingleResult())[0]).intValue());
I'm sending a little maven project which reproduces the bug.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:25 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-5419) COUNT operator with composite primary key and JPA 2.0 Criteria API produces bad sql
[
https://hibernate.onjira.com/browse/HHH-5419?page=com.atlassian.jira.plug...
]
Jeremy Whiting commented on HHH-5419:
-------------------------------------
We have been using the MySQL InnoDB dialect.
COUNT operator with composite primary key and JPA 2.0 Criteria API
produces bad sql
-----------------------------------------------------------------------------------
Key: HHH-5419
URL: https://hibernate.onjira.com/browse/HHH-5419
Project: Hibernate ORM
Issue Type: Bug
Affects Versions: 3.5.4, 3.6.0.Beta1, 4.0.0.CR3
Environment: hibernate-entitymanager 3.6.0.Beta1, glassfish 3.0.1, linux ubuntu
10.04, MS SQL Server 2008
Reporter: Fabio Braga de Oliveira
Assignee: John Verhaeg
Priority: Minor
Fix For: 4.0.0.CR4, 4.0.0.CR5
Attachments: hibernate-count-bug.zip
Hibernate produces a invalid SQL if anyone use the count() operator with the JPA 2.0
Criteria API. Code:
CriteriaBuilder cb = getEntityManager().getCriteriaBuilder();
CriteriaQuery<Object[]> cq = cb.createQuery(Object[].class);
Root<EntityCompositePK> r = cq.from(EntityCompositePK.class);
cq.multiselect(cb.count(r));
assertEquals(0, ((Long)
(getEntityManager().createQuery(cq).getSingleResult())[0]).intValue());
I'm sending a little maven project which reproduces the bug.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:26 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-5419) COUNT operator with composite primary key and JPA 2.0 Criteria API produces bad sql
[
https://hibernate.onjira.com/browse/HHH-5419?page=com.atlassian.jira.plug...
]
Ståle W. Pedersen commented on HHH-5419:
----------------------------------------
hi, i created a test case that confirm that count query with EmbeddedId use all Id's
in the argument. the test also do a count for a class using ClassId which create a sql
that only use one Id.
I havent figured out how to fetch the sql to the test, so you have to view the log to
confirm atm.
https://github.com/stalep/hibernate-orm/commit/54911765de7981ec9a2318fc99...
COUNT operator with composite primary key and JPA 2.0 Criteria API
produces bad sql
-----------------------------------------------------------------------------------
Key: HHH-5419
URL: https://hibernate.onjira.com/browse/HHH-5419
Project: Hibernate ORM
Issue Type: Bug
Affects Versions: 3.5.4, 3.6.0.Beta1, 4.0.0.CR3
Environment: hibernate-entitymanager 3.6.0.Beta1, glassfish 3.0.1, linux ubuntu
10.04, MS SQL Server 2008
Reporter: Fabio Braga de Oliveira
Assignee: John Verhaeg
Priority: Minor
Fix For: 4.0.0.CR4, 4.0.0.CR5
Attachments: hibernate-count-bug.zip
Hibernate produces a invalid SQL if anyone use the count() operator with the JPA 2.0
Criteria API. Code:
CriteriaBuilder cb = getEntityManager().getCriteriaBuilder();
CriteriaQuery<Object[]> cq = cb.createQuery(Object[].class);
Root<EntityCompositePK> r = cq.from(EntityCompositePK.class);
cq.multiselect(cb.count(r));
assertEquals(0, ((Long)
(getEntityManager().createQuery(cq).getSingleResult())[0]).intValue());
I'm sending a little maven project which reproduces the bug.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-5419) COUNT operator with composite primary key and JPA 2.0 Criteria API produces bad sql
[
https://hibernate.onjira.com/browse/HHH-5419?page=com.atlassian.jira.plug...
]
Ståle W. Pedersen commented on HHH-5419:
----------------------------------------
i created a jira issue on as7 here; https://issues.jboss.org/browse/AS7-4135
COUNT operator with composite primary key and JPA 2.0 Criteria API
produces bad sql
-----------------------------------------------------------------------------------
Key: HHH-5419
URL: https://hibernate.onjira.com/browse/HHH-5419
Project: Hibernate ORM
Issue Type: Bug
Affects Versions: 3.5.4, 3.6.0.Beta1, 4.0.0.CR3
Environment: hibernate-entitymanager 3.6.0.Beta1, glassfish 3.0.1, linux ubuntu
10.04, MS SQL Server 2008
Reporter: Fabio Braga de Oliveira
Assignee: John Verhaeg
Priority: Minor
Fix For: 4.0.0.CR4, 4.0.0.CR5
Attachments: hibernate-count-bug.zip
Hibernate produces a invalid SQL if anyone use the count() operator with the JPA 2.0
Criteria API. Code:
CriteriaBuilder cb = getEntityManager().getCriteriaBuilder();
CriteriaQuery<Object[]> cq = cb.createQuery(Object[].class);
Root<EntityCompositePK> r = cq.from(EntityCompositePK.class);
cq.multiselect(cb.count(r));
assertEquals(0, ((Long)
(getEntityManager().createQuery(cq).getSingleResult())[0]).intValue());
I'm sending a little maven project which reproduces the bug.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:15 p.m.
New subject: [Hibernate-JIRA] Assigned: (HHH-5419) COUNT operator with composite primary key and JPA 2.0 Criteria API produces bad sql
[
https://hibernate.onjira.com/browse/HHH-5419?page=com.atlassian.jira.plug...
]
Gail Badner reassigned HHH-5419:
--------------------------------
Assignee: Gail Badner (was: John Verhaeg)
COUNT operator with composite primary key and JPA 2.0 Criteria API
produces bad sql
-----------------------------------------------------------------------------------
Key: HHH-5419
URL: https://hibernate.onjira.com/browse/HHH-5419
Project: Hibernate ORM
Issue Type: Bug
Affects Versions: 3.5.4, 3.6.0.Beta1, 4.0.0.CR3
Environment: hibernate-entitymanager 3.6.0.Beta1, glassfish 3.0.1, linux ubuntu
10.04, MS SQL Server 2008
Reporter: Fabio Braga de Oliveira
Assignee: Gail Badner
Priority: Minor
Fix For: 4.0.0.CR4, 4.0.0.CR5
Attachments: hibernate-count-bug.zip
Hibernate produces a invalid SQL if anyone use the count() operator with the JPA 2.0
Criteria API. Code:
CriteriaBuilder cb = getEntityManager().getCriteriaBuilder();
CriteriaQuery<Object[]> cq = cb.createQuery(Object[].class);
Root<EntityCompositePK> r = cq.from(EntityCompositePK.class);
cq.multiselect(cb.count(r));
assertEquals(0, ((Long)
(getEntityManager().createQuery(cq).getSingleResult())[0]).intValue());
I'm sending a little maven project which reproduces the bug.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:17 p.m.
New subject: [Hibernate-JIRA] Assigned: (HHH-5419) COUNT operator with composite primary key and JPA 2.0 Criteria API produces bad sql
[
https://hibernate.onjira.com/browse/HHH-5419?page=com.atlassian.jira.plug...
]
Gail Badner reassigned HHH-5419:
--------------------------------
Assignee: John Verhaeg (was: Gail Badner)
COUNT operator with composite primary key and JPA 2.0 Criteria API
produces bad sql
-----------------------------------------------------------------------------------
Key: HHH-5419
URL: https://hibernate.onjira.com/browse/HHH-5419
Project: Hibernate ORM
Issue Type: Bug
Affects Versions: 3.5.4, 3.6.0.Beta1, 4.0.0.CR3
Environment: hibernate-entitymanager 3.6.0.Beta1, glassfish 3.0.1, linux ubuntu
10.04, MS SQL Server 2008
Reporter: Fabio Braga de Oliveira
Assignee: John Verhaeg
Priority: Minor
Fix For: 4.0.0.CR4, 4.0.0.CR5
Attachments: hibernate-count-bug.zip
Hibernate produces a invalid SQL if anyone use the count() operator with the JPA 2.0
Criteria API. Code:
CriteriaBuilder cb = getEntityManager().getCriteriaBuilder();
CriteriaQuery<Object[]> cq = cb.createQuery(Object[].class);
Root<EntityCompositePK> r = cq.from(EntityCompositePK.class);
cq.multiselect(cb.count(r));
assertEquals(0, ((Long)
(getEntityManager().createQuery(cq).getSingleResult())[0]).intValue());
I'm sending a little maven project which reproduces the bug.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4500
days inactive
5094
days old
hibernate-issues@lists.jboss.org
17 comments
8 participants
participants (8)
-
Anne Buit (JIRA) -
Fabio Braga de Oliveira (JIRA)
-
Gail Badner (JIRA)
-
Jeremy Whiting (JIRA)
-
John Verhaeg (JIRA)
-
Oliver Gierke (JIRA)
-
Steve Ebersole (JIRA)
-
Ståle W. Pedersen (JIRA)