|
||||||||
|
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 |
||||||||
|
||||||||
|
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 |
||||||||
Noel, these are better because they are concrete. Thanks.
1) Have you looked at subselect fetching? There are some limitations to it, but it is more in-line with what you are looking for there. So instead of @BatchSize you'd use @org.hibernate.annotations.Fetch(org.hibernate.annotations.FetchMode.SUBSELECT)
2) Not against this, but please note just how vastly different that is then this request. So propose an API. Or better yet, develop a proposal and send us a pull request.
As I said, I am not even really against this issue as a whole; its just not doable given the current code. And it might not ever be in terms of splitting. Ok, sure I can see use of temp tables possibly working there, but I would just point out how much trouble we have with our existing use of temp tables due to the extremely differing support for temp tables across databases. So in theory it sounds great, but in practice I expect difficulties.