Received: from mailout00.sul.t-online.com (mailout00.sul.t-online.com [194.25.134.16]) by hub.org (8.10.1/8.10.1) with ESMTP id e6CD7gW16355 for ; Wed, 12 Jul 2000 09:07:42 -0400 (EDT) Received: from fwd01.sul.t-online.com by mailout00.sul.t-online.com with smtp id 13CMEg-0000tG-01; Wed, 12 Jul 2000 15:07:34 +0200 Received: from hot.jw.home (340000654369-0001@[62.224.109.179]) by fwd01.sul.t-online.com with esmtp id 13CMER-07XC5oC; Wed, 12 Jul 2000 15:07:19 +0200 Received: (from wieck@localhost) by hot.jw.home (8.8.5/8.8.5) id NAA23462; Wed, 12 Jul 2000 13:41:13 +0200 From: JanWieck@t-online.de (Jan Wieck) Message-Id: <200007121141.NAA23462@hot.jw.home> Subject: Re: Opposite of LOCK In-Reply-To: from Antti Linno at "Jul 12, 2000 11:11:03 am" To: Antti Linno Date: Wed, 12 Jul 2000 13:41:13 +0200 (MEST) CC: pgsql-sql@postgresql.org Reply-To: Jan Wieck X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Sender: 340000654369-0001@t-dialin.net X-Archive-Number: 200007/126 Antti Linno wrote: > Is there any possibility to unlock tables after they've been locked? The > manual part of lock was fuzzy, so I ask from experts instead. MySQL > uses lock and unlock. Yes, COMMIT/ROLLBACK. The transactional concept implies that you hold each lock you accquired since transaction start until the transaction ends. Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== JanWieck@Yahoo.com #