Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 75073 invoked from network); 22 Nov 2005 20:01:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 22 Nov 2005 20:01:35 -0000 Received: (qmail 63373 invoked by uid 500); 22 Nov 2005 20:01:34 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 63020 invoked by uid 500); 22 Nov 2005 20:01:33 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 63009 invoked by uid 99); 22 Nov 2005 20:01:33 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Nov 2005 12:01:33 -0800 Received-SPF: pass (asf.osuosl.org: local policy) Received: from [192.18.98.34] (HELO brmea-mail-3.sun.com) (192.18.98.34) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Nov 2005 12:03:05 -0800 Received: from fe-amer-09.sun.com ([192.18.108.183]) by brmea-mail-3.sun.com (8.12.10/8.12.9) with ESMTP id jAMK1C3F015146 for ; Tue, 22 Nov 2005 13:01:12 -0700 (MST) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) id <0IQD00G01EEGBY00@mail-amer.sun.com> (original mail from Mehran.Sowdaey@Sun.COM) for derby-user@db.apache.org; Tue, 22 Nov 2005 13:01:12 -0700 (MST) Received: from Sun.COM ([129.147.9.36]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPSA id <0IQD004SHGXOCJIB@mail-amer.sun.com> for derby-user@db.apache.org; Tue, 22 Nov 2005 13:01:00 -0700 (MST) Date: Tue, 22 Nov 2005 13:01:00 -0700 From: Mehran Sowdaey Subject: Re: table locking In-reply-to: <43836274.2010108@sbcglobal.net> Sender: Mehran.Sowdaey@Sun.COM To: Derby Discussion Reply-to: Mehran.Sowdaey@Sun.COM Message-id: <438378FC.1000702@Sun.COM> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en References: <438344B6.2000003@Sun.COM> <43836274.2010108@sbcglobal.net> User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.4) Gecko/20041214 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Please see: (Table 2). This is a 10.0 document but we have seen the same in 10.1 thanks, ------- mehran Mike Matrigali wrote On 11/22/05 11:24,: > Derby uses row locking by default, can you please explain why you > think it is table locking. Derby does get table level intent locks, > to enable the row locking feature - so for instances when updating > a row in a table you will get a table level IX and a row level X, but > another transaction will also be able to get a table level IX and a > row level X lock on another row. > > There are situations depending on isolation level and lock escalation > where real table level locks are requested, not sure if you are running > into that. More information is needed. > > Mehran Sowdaey wrote: > >>Hi, >> >>When running derby in server mode if autocommit is turned off table >>locking occurs. Is there anyway to prevent that and have row level >>locking. We have tried changing a few of derby parameters without success. >> >>thanks, >>------- >>mehran >> >> >> > > -- Mehran Sowdaey Sun Microsystems, Inc. Mailstop UBRM06-304 500 Eldorado Blvd. Broomfield, CO. 80021 Pager: 1-800-759-8352 (PIN 1855303) Phone: 303-272-3192