Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1050477714.1141137643754.JavaMail.jira@ajax.apache.org>
Date: Tue, 28 Feb 2006 15:40:43 +0100 (CET)
From: "Andreas Korneliussen (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Created: (DERBY-1068) change of store contract: online
 compress operations should not share any locks with user transactions
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

change of store contract: online compress operations should not share any locks with user transactions
------------------------------------------------------------------------------------------------------

         Key: DERBY-1068
         URL: http://issues.apache.org/jira/browse/DERBY-1068
     Project: Derby
        Type: Improvement
  Components: Store  
    Reporter: Andreas Korneliussen
    Priority: Minor


Propose to add the following to the store contract:
* truncate and compress requires exclusive table locking
* the truncate, purge and compress operations do not share any locks with user transactions 

Currently the store implementation allows users to share locks in truncate and possibly purge.

This request is driven by:
http://www.nabble.com/conflict-detection-strategies-t1120376.html#a2938142

and:

http://www.nabble.com/RowLocation-contract-from-storage-engine-t1142235.html#a2994156

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira