[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2408?page=c...
]
Olivier Wehner commented on HHH-2408:
-------------------------------------
Hi, just some additional information to stress that this is indeed an issue:
- As pointed out in the title, this concerns a JPA/QL query, NOT HQL. The statement is
legal and must run without further acrobatics.
- This issue is as well described in the following forum entry:
http://forum.hibernate.org/viewtopic.php?p=2314896&sid=f4d3c8f74d63d6...
- We observed the same with hibernate 3.2 and Oracle 9i (using
org.hibernate.dialect.Oracle9Dialect).
- At the bottom line stands: JPA/QL updates do not work with nested properties in where
clause (on Oracle?). I'd say this is a rather serious one.
Best regards,
Olivier
Incorrect SQL generated for JPA QL Update statement involving
multiple entities
-------------------------------------------------------------------------------
Key: HHH-2408
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2408
Project: Hibernate3
Issue Type: Bug
Affects Versions: 3.2.2
Environment: Hibernate 3.2.2 GA, Oracle 9i
Reporter: Alex Savitsky
Attachments: application.properties, Branch.java, Issue.java, log.txt,
PersistentEntity.java, TestCase.zip, Visit.java
When generating SQL for statements like this: UPDATE Issue i SET i.dueDate = i.dueDate +
10 WHERE i.visit.branch.id = :branchId, an extra comma is generated at the end of table
list: update Issue, set DUE_DATE=DUE_DATE+10 where BRANCH_ID=?
--
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