I had an interesting epiphany... I am not sure that it really ever makes sense to wrap the isolated table DDL in a new transaction. In the work-around code above, that is the purpose of the false that I pass in to the delegateWork method. That argument says whether to wrap the work in a new transaction after the current transaction is suspended. Not sure it ever makes sense for that to be non-null. Anyway, I went ahead and made that false all the time for now. Lets see what the CI tests show...
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
I had an interesting epiphany... I am not sure that it really ever makes sense to wrap the isolated table DDL in a new transaction. In the work-around code above, that is the purpose of the false that I pass in to the delegateWork method. That argument says whether to wrap the work in a new transaction after the current transaction is suspended. Not sure it ever makes sense for that to be non-null. Anyway, I went ahead and made that false all the time for now. Lets see what the CI tests show...