[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3538?page=c...
]
Shawn Clowater commented on HHH-3538:
-------------------------------------
I don't know what I was smoking with my previous comment. Even w/o the explicit
fetching it can throw off your paging. I think I was trying to reduce the amount of data
coming back from a query one day and had noticed that I was getting a bunch of dupes in my
results prior to getting to the distinct result transformer and a bad synapse fired in my
brain.
Criteria.createAlias/Criteria.createCriteria forces join fetching of
association
--------------------------------------------------------------------------------
Key: HHH-3538
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3538
Project: Hibernate Core
Issue Type: Bug
Components: query-criteria
Affects Versions: 3.2.6, 3.3.1
Reporter: Hauke Rabe
Assignee: Steve Ebersole
Fix For: 3.5.x
Attachments: hhh-3538.zip, hhh-3538b.zip
The underlying cause is an invalid assumption made in JoinWalker that every association
found in its association member list is to be fetched (added to the select fragment).
--
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