|
||||||||
|
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 |
||||||||
Why don't we fix this? For each DB the implementation can be different, that's the idea of a framework like Hibernate to hide the detail of how this is done.
The specification is very simple. You have an IN clause, and you want it to work on any DB for any length. If the default/stupid implementation in shitty DB is to call the db for each ID I don't care. What I care about is that I don't need to write workaround for each project I work on!
By the way, we should have cache hit, if the IN is about the the primary key.
Are we French? This is dragging with too much talking.