[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-530?page=co...
]
Shawn Clowater commented on HHH-530:
------------------------------------
Blast from the past. Forgot all about this until I jacked in the patch for the
createAlias for Subqueries for a coworker today. Then noticed that filters weren't
applied to the joins. And then when I touched that up, the incorrect binding order.
This is definitely a show stopper for me, I either need this or the ability to specify the
same association twice in 2 separate createAlias calls. I guess the other alternative
would be HQL w/o the use of subqueries.
I'll be investigating applying the above patch in the morning (which for me is 12
hours) to a 3.2.5 jar. If more work is needed for this I can be available for either
development and/or guinea pig, we've got a bunch of filters being used so if something
comes off the rails it should be pretty apparent.
Better handling of filter params in HQL to allow filter use on
subqueries
-------------------------------------------------------------------------
Key: HHH-530
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-530
Project: Hibernate3
Issue Type: Bug
Components: core
Reporter: Gavin King
Assignee: Steve Ebersole
Attachments: hibernate_filter_fix-3.0.5.patch,
hibernate_filter_fix-3.0.5_14.patch
Currently filter conditions are applied in subselects, they should not be.
--
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....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira