]
Julien HENRY updated HHH-1570:
------------------------------
Attachment: HHH-1570-fix.patch
Experimental patch that fix the issue but introduce a regression in
FumTest#testKeyManyToOne()
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: 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.
-
If you think it was sent incorrectly contact one of the administrators: