[hibernate-issues] [Hibernate-JIRA] Updated: (HHH-1570) criteria-api: filtering by key-many-to-one causes invalid sql

[Yoann Antoviaque (JIRA)]

     [ https://hibernate.onjira.com/browse/HHH-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yoann Antoviaque updated HHH-1570:
----------------------------------

    Attachment: HHH-1570-fix-composites.diff

patch based on HHH-1570-fix.patch which was not working in our case with multiple association in the same composite key

> criteria-api: filtering by key-many-to-one causes invalid sql
> -------------------------------------------------------------
>
>                 Key: HHH-1570
>                 URL: https://hibernate.onjira.com/browse/HHH-1570
>             Project: Hibernate ORM
>          Issue Type: Bug
>          Components: query-criteria
>    Affects Versions: 3.5.3, 3.6.0.Beta1
>            Reporter: Joris Verschoor
>            Assignee: Steve Ebersole
>         Attachments: HHH-1570-fix-composites.diff, HHH-1570-fix.patch, HHH-1570-it.patch, hibernate.patch
>
>
> We have a class Price that has a composite-id using a couple of key-properties and some key-many-to-ones)
> One of those is "transportation", which has a many-to-one to transportationType
> When we query using: criteria.add(Expression.eq("price.transportation.transportationType.id", transId);, we get an invalid SQL statement: The table of transportation was not selected.
> I will try to make a testcase today or tomorrow, depending on my schedule.. Things will be more clear by then...
> We have created a work-around, by mapping the transportationID twice: once in key-property, and once as a many-to-one. (instead of one key-many-to-one)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira