[
https://issues.apache.org/jira/browse/TORQUE-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Fox resolved TORQUE-222.
-------------------------------
Resolution: Fixed
Fix Version/s: 4.0-beta1
> Change unlock table behaviour in MSSQL
> --------------------------------------
>
> Key: TORQUE-222
> URL: https://issues.apache.org/jira/browse/TORQUE-222
> Project: Torque
> Issue Type: Improvement
> Components: Runtime
> Reporter: Thomas Fox
> Assignee: Thomas Fox
> Fix For: 4.0-beta1
>
>
> Cunnently, the MSSQL implementation of unlockTable issues a commit, which
> actually releases all locks on all tables. It also has a few problems:
> - if the user wanted a rollback instead of a commit, it will not be possible
> because a commit has already been issued previously
> - if the connection is in autocommit mode, unlock will throw an error.
> The unlock table implementation in MSSQL should be changed to do nothing.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
