[hibernate-issues] [Hibernate-JIRA] Updated: (HHH-5106) UnsupportedOperationException on SQL named native queries

[Emmanuel Bernard (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Bernard updated HHH-5106:
----------------------------------

    Summary: UnsupportedOperationException on SQL named native queries  (was: Getting UnsupportedOperationException("not yet implemented for SQL queries") for Named Native queries)

> UnsupportedOperationException on SQL named native queries
> ---------------------------------------------------------
>
>                 Key: HHH-5106
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5106
>             Project: Hibernate Core
>          Issue Type: Bug
>          Components: entity-manager
>    Affects Versions: 3.5.0-Final
>            Reporter: Zuber Saiyed
>            Assignee: Emmanuel Bernard
>             Fix For: 3.5.x
>
>
> I want to bring following to your attention that in org.hibernate.ejb.AbstractEntityManagerImpl method createNamedQuery: 
> 	
> org.hibernate.Query namedQuery = getSession().getNamedQuery( name ); // instance of SQLQueryImpl being returned for native query
> try {
> // As SQLQueryImpl's getReturnTypes() method throws UnsupportedOperationException, named native queries are not working in Core 3.5-Final
>     if ( namedQuery.getReturnTypes().length != 1 ) {
>      throw new IllegalArgumentException( "Cannot create TypedQuery for query with more than one return" );
>     }

-- 
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.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira