db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Fox (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (TORQUE-222) Change unlock table behaviour in MSSQL
Date Wed, 29 Aug 2012 03:33:07 GMT

     [ https://issues.apache.org/jira/browse/TORQUE-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Thomas Fox reassigned TORQUE-222:

    Assignee: Thomas Fox
> 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
> 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: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org

View raw message