Mailing-List: contact torque-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Torque Developers List" <torque-dev@db.apache.org>
Date: Wed, 29 Aug 2012 14:33:07 +1100 (NCT)
From: "Thomas Fox (JIRA)" <jira@apache.org>
To: torque-dev@db.apache.org
Message-ID: <1027313949.10104.1346211187721.JavaMail.jiratomcat@arcas>
In-Reply-To: <979061586.10103.1346211187641.JavaMail.jiratomcat@arcas>
Subject: [jira] [Assigned] (TORQUE-222) Change unlock table behaviour in
 MSSQL
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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