|
||||||||
|
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 |
||||||||
After some additional contemplation, I think it is better for the time being to have any attempt to request locking against oracle use follow up locking. There are just too many cases where oracle is going to barf because it does not like locking in conjunction with this or that other SQL feature and because currently we do not have enough semantic knowldge of the query to recognize all such situations anyway (at least until SQL generation is moved from String-based to AST-based).