[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2408?page=c...
]
Alex Savitsky commented on HHH-2408:
------------------------------------
My bad for not checking the docs. However, if an operation is not supported, a general
expectation is to receive an UnsupportedOperationException (or something alike) at the
time the query is parsed (it was a @NamedQuery, so that would be the startup time), rather
than a cryptic DB-specific message during runtime execution, wouldn't you agree?
Regards,
Alex
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