[seam-issues] [JBoss JIRA] Commented: (JBSEAM-4744) EntityQuery.resultList throws a exception when the entity has composite key

[Marek Novotny (JIRA)]

    [ https://issues.jboss.org/browse/JBSEAM-4744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570263#comment-12570263 ] 

Marek Novotny commented on JBSEAM-4744:
---------------------------------------

Please don't set Fix Version field, this field is only for committers.

> EntityQuery.resultList throws a exception when the entity has composite key
> ---------------------------------------------------------------------------
>
>                 Key: JBSEAM-4744
>                 URL: https://issues.jboss.org/browse/JBSEAM-4744
>             Project: Seam
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: 2.2.0.GA, 2.2.1.CR1
>         Environment: Fedora 12, JDK 1.6 sun/oracle, Seam 2.2.1 CR1, MySQL 5
>            Reporter: Alessandro Lazarotti
>              Labels: entity-query, hibernate
>             Fix For: 2.2.1.Final
>
>
> Hibernate has a known trouble running queries using "count" when the entity has composite keys, like: 
>    select count(foobar) from Foobar foobar:
>  - ERROR [JDBCExceptionReporter] Operand should contain 1 column(s)
> Seam EntityQuery has a workaround, using count(*) instead of count(alias)(spec way) if you use entityQuery.resultCount. 
> It's works with Seam 2.0.x but no more in Seam 2.2.x

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira