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

[Jeff Schenk (JIRA)]

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


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