[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1657?page=c...
]
Peter Lupo commented on HHH-1657:
---------------------------------
It certainly worths a try.
Even though the ORDER BY problem seems to be another problem, it seems to manifest because
of the missing table qualifer. The code may have to be changed elsewhere to get this fixed
but I guess it would be the very same issue and it should be treated together with this
one, doesn't it?
I mean... the problem seems to be "unqualified columns on multi-table queries with
the joined subclass strategy", may it manifest on the WHERE clause or the ORDER BY
clause.
hql update generate wrong sql with joined subclass hierarcy
-----------------------------------------------------------
Key: HHH-1657
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1657
Project: Hibernate3
Issue Type: Bug
Components: query-hql
Environment: Hibernate 3.2.0cr1, Hibernate 3.1.3
Reporter: Alexey Romanchuk
Assignee: Gail Badner
Priority: Critical
Fix For: 3.2.x, 3.3.0
Let suppose that we have two joined subclass entities: Parent (id PK) and Child (id PK)
that mapped with joined subclass method.
When I try to update Child by id with hql:
update Child c set c.field = 'value' where c.id = 1234
hibernate generates joined tables like
insert into HT_parent select child0_.id as id from child child0_ inner join parent
child0_1_ on child0_.id=child0_1_.id wher id in = 1234
look at last condition. hibernate use id WITH OUT tables alias that cause sql exception:
column reference "id" is ambiguous
--
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