1) if the entire result set is not scrolled, then an exception occurs on session flush;
2) when the block of rows is processed for the current entity, the row following the block (for the next entity) is also processed; an exception is thrown if the join fetched collection for that next entity is accessed.
I've created a pull request with a different fix.
Please try it out and let us know if it works for you.
Thanks,
Gail
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
There are some side effects with the patch:
1) if the entire result set is not scrolled, then an exception occurs on session flush;
2) when the block of rows is processed for the current entity, the row following the block (for the next entity) is also processed; an exception is thrown if the join fetched collection for that next entity is accessed.
I've created a pull request with a different fix.
Please try it out and let us know if it works for you.
Thanks,
Gail