Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 6349 invoked from network); 23 Feb 2006 14:08:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 23 Feb 2006 14:08:06 -0000 Received: (qmail 9975 invoked by uid 500); 23 Feb 2006 14:08:02 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 9739 invoked by uid 500); 23 Feb 2006 14:08:01 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 9730 invoked by uid 99); 23 Feb 2006 14:08:01 -0000 X-ASF-Spam-Status: No, hits=1.3 required=10.0 tests=SPF_FAIL X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Feb 2006 06:08:01 -0800 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 6E742DF for ; Thu, 23 Feb 2006 15:07:40 +0100 (CET) Message-ID: <1048752676.1140703660450.JavaMail.jira@ajax.apache.org> Date: Thu, 23 Feb 2006 15:07:40 +0100 (CET) From: "Kathey Marsden (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Created: (DERBY-1040) Run store locking tests with network server and investigate locking behaviour MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Run store locking tests with network server and investigate locking behaviour ------------------------------------------------------------------------------ Key: DERBY-1040 URL: http://issues.apache.org/jira/browse/DERBY-1040 Project: Derby Type: Sub-task Components: Network Server, Network Client Versions: 10.2.0.0 Reporter: Kathey Marsden The store locking tests should be run with network server, locking behaviour investigated, and a perhaps a proposal made for testing locking with network server. For network server, the prefecting of data causes diffs in the tests and I am not sure if this is expected or not. I noticed for example such diffs in updatelocks.sql and readlocks.sql. Below is the list of locking tests I see in store. Feel free to take one or two and file a subtask. EscalateLock.sql RowLockBasic.sql RowLockIso.sql TableLockBasic.sql TableLockBasic.subsql lockTableVti.sql readBtreeCursorLocks.subsql readBtreeSetLocks.subsql readCursorLocks.subsql readSetLocks.subsql readlocks.sql updateBtreeCursorLocks.subsql updateBtreeHoldCursorLocksJDBC30.subsql updateBtreeSetLocks.subsql updatecursorlocks.subsql updateholdcursorlocksJDBC30.subsql updatelocks.sql updatelocksJDBC30.sql updatesetlocks.subsql RowLockIso.sql rlliso1multi.sql rlliso1multi.subsql rlliso2multi.sql rlliso3multi.sql -- 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