From: <no...@at...> - 2005-07-19 23:28:38
|
Message: The following issue has been closed. Resolver: Gavin King Date: Tue, 19 Jul 2005 6:26 PM Thanks, fixed. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/browse/HHH-708 Here is an overview of the issue: --------------------------------------------------------------------- Key: HHH-708 Summary: Restrictions.in could not be used properly on composite-ids Type: Bug Status: Closed Priority: Major Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: Hibernate3 Components: core Fix Fors: 3.1 beta Versions: 3.0.5 Assignee: Reporter: Holger Bartnick Created: Tue, 5 Jul 2005 10:22 AM Updated: Tue, 19 Jul 2005 6:26 PM Environment: Oracle 9i, org.hibernate.criterion.InExpression Description: Restrictions.in could not be used properly on composite-ids for a composite-id with the attributes key and station the resulting sql is like: [where key in (?,?...) and station in (?,?...)] it should result in an sql like: [where (key, station) in ((?,?),(?,?)...)] otherwise the result would be a scalar product example: key station 1 1 2 1 2 2 3 2 [where key in (1,2,3) and station in (1,2)] would return all values [where (key, station) in ((1,1),(2,1),(3,2))] would omit the record (2,2) --------------------------------------------------------------------- JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |