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

[Sanchit Srivastava (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32089#action_32089 ] 

Sanchit Srivastava commented on HHH-1570:
-----------------------------------------

I am using 3.2.6.ga version of hibernate and am still finding this issue...
So i am unable to move along the association using a key-many-to-one association from table A to B (A contains composite key pointing to B and C tables)

I tried using both criteria.createAlias and criteria.createCriteria ..... Using createAlias, as pointed out earlier, is creeating a wrong query (where clause b.property=? is created but the table B is missing from 'from clause' ).
However createCriteria is not even creating the where clause...

Do we have a fix for this on way or the Hibernate team is still working ... I find that the issue is still open, with no fix version specified.. so I assume this true.... Please can you provide a statuc on this?

Regards & Thanks

> criteria-api: filtering by key-many-to-one causes invalid sql
> -------------------------------------------------------------
>
>                 Key: HHH-1570
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1570
>             Project: Hibernate Core
>          Issue Type: Bug
>          Components: query-criteria
>    Affects Versions: 3.1.2
>            Reporter: Joris Verschoor
>         Attachments: 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.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira