Return-Path: Delivered-To: apmail-db-torque-dev-archive@www.apache.org Received: (qmail 7796 invoked from network); 28 Mar 2005 11:21:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 28 Mar 2005 11:21:03 -0000 Received: (qmail 16034 invoked by uid 500); 28 Mar 2005 11:21:03 -0000 Delivered-To: apmail-db-torque-dev-archive@db.apache.org Received: (qmail 15868 invoked by uid 500); 28 Mar 2005 11:21:02 -0000 Mailing-List: contact torque-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Apache Torque Developers List" Reply-To: "Apache Torque Developers List" Delivered-To: mailing list torque-dev@db.apache.org Received: (qmail 15855 invoked by uid 99); 28 Mar 2005 11:21:02 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from mail.seitenbau.net (HELO mail.seitenbau.net) (194.175.229.106) by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 28 Mar 2005 03:21:01 -0800 Received: from [195.127.188.18] (helo=www.seitenbau.net) by router1.seitenbau.net with esmtp (Exim 4.43) id 1DFsJY-0005Hf-QU for torque-dev@db.apache.org; Mon, 28 Mar 2005 13:21:48 +0200 In-Reply-To: <4247E21C.8020108@numerixtechnology.de> Subject: Re: deprecate lockTable() and unlockTable() methods in adapter To: "Apache Torque Developers List" X-Mailer: Lotus Notes Release 6.0 September 26, 2002 Message-ID: From: Thomas Fischer Date: Mon, 28 Mar 2005 13:21:01 +0200 X-MIMETrack: Serialize by Router on www/seitenbau(Release 6.5.1|January 21, 2004) at 28.03.2005 01:21:00 PM MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: quoted-printable X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi Tarlika, it seems that everything in Torque is used by somebody - no chance to c= lear up ;-) Ok, I will not do it. By the way, why do you need to lock tables ? I thought postgresql is capable of serializable transactions. In my experience, locking is only= needed if one does not have serializable transactions (or does not want= to use them). Thomas T E Schmitz schrieb am 28.03.2005 12:53:= 16: > Hello Thomas, > > Thomas Fischer wrote: > > I have noticed that the adapter contains two methods, lockTable() a= nd > > unlockTable(), which are not used by Torque (anymore ?). The implementation > > of these methods is in some cases not existant, in other cases questionable > > (e.g. in Oracle, tables are unlocked by a commit, so the unlockTabl= e does a > > commit, which is not at all the expected behaviour.) > > > > It seems that locking and unlocking a table cannot be made to look = the same > > over all Dbs. To reflect this, I would like to deprecate these meth= ods in > > order to remove them in a future release (Torque 3.3 at the soonest= ). Any > > objections ? > > Yes - I am using them. Although: I wish I had a better concept avoidi= ng > lock table for my particular scenario. > > > -- > > > Regards/Gru=DF, > > Tarlika Elisabeth Schmitz >= --------------------------------------------------------------------- To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org For additional commands, e-mail: torque-dev-help@db.apache.org