|
||||||||
|
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 |
||||||||
So the prepare / release would be for session setup / teardown.
The prepareForUse / releaseFromUse would be called immediately before the bulk update select and immediately after the deletes are complete.
One thing I did think of on my drive home today Steve...
I run Hibernate in a cluster where each instance is unaware of the other instances.
In the case of PostgreSQL, where the temp tables aren't prepared-transaction happy, if we're using global tables setup in prepare / release, there will have to be some mechanism to ensure that only the first instance to start creates tables, and only the last one stop destroys them...