[hibernate-issues] [Hibernate-JIRA] Updated: (HHH-5579) After upgrading from 3.3.2.GA to 3.5.6.Final receiving numerous ORA-00918: column ambiguously defined Exceptions

[tony o'grady (JIRA)]

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

tony o'grady updated HHH-5579:
------------------------------

    Attachment: Hibernate_SQL_HHH-5579.txt
                Hibernate_StackTrace_HHH-5579.txt
                TestCase_for_Hibernate_Core_Issue_HHH-5579.zip

I'm attaching a test case for this issue, as a maven project. It is the same test cast I uploaded for HHH-951


The test environment:

Oracle DB Server: 10.2.0.4
Hibernate Core: 3.5.6-Final
Java: Sun JDK 1.6.20
Eclipse workspace: Eclipse Helios WTP
Maven plugin for Eclipse: Sonatype, Inc. Maven Integration for Eclipse, 0.10.2.20100623-1649

Same error with Hibernate Core versions: 3.3.0.GA, 3.3.2.GA., 3.6.0.Final 

> After upgrading from 3.3.2.GA to 3.5.6.Final receiving numerous ORA-00918: column ambiguously defined Exceptions
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: HHH-5579
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5579
>             Project: Hibernate Core
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.5.6
>         Environment: Hibernate 3.5.6, Spring 3.0.4.RELEASE, Oracle 11g2
>            Reporter: Jeff Schenk
>         Attachments: Hibernate_SQL_HHH-5579.txt, Hibernate_StackTrace_HHH-5579.txt, TestCase_for_Hibernate_Core_Issue_HHH-5579.zip
>
>
> After upgrading from 3.3.2.GA to 3.5.6.Final receiving numerous ORA-00918: column ambiguously defined Exceptions.
> After research it appears to be linked to:
> Per HHH-951 setMaxResults causes "ORA-00918: column ambiguously defined" exception 
> http://opensource.atlassian.com/projects/hibernate/browse/HHH-951
> I removed the MaxResults projects as per HHH-951 and I was able to get past that one query, but had to back out until this regression is resolved.

-- 
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