[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-2408) Incorrect SQL generated for JPA QL Update statement involving multiple entities

Istvan Kovacs (JIRA) noreply at atlassian.com
Thu Feb 16 10:15:12 EST 2012


    [ https://hibernate.onjira.com/browse/HHH-2408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45530#comment-45530 ] 

Istvan Kovacs commented on HHH-2408:
------------------------------------

Steve,

thanks for the explanation. Maybe an enhancement to reject the invalid query would make this less confusing; generating invalid SQL is hardly the solution. I know, 'garbage in, garbage out', but from another point of view, we expect parsers to validate syntax (e.g. you wouldn't like javac to generate invalid byte code if you make a syntax error in your source).

Kofa

> Incorrect SQL generated for JPA QL Update statement involving multiple entities
> -------------------------------------------------------------------------------
>
>                 Key: HHH-2408
>                 URL: https://hibernate.onjira.com/browse/HHH-2408
>             Project: Hibernate ORM
>          Issue Type: Bug
>          Components: query-hql
>    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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the hibernate-issues mailing list