Received: from mx99.openu.ac.il (arbel.openu.ac.il [147.233.32.4]) by hub.org (8.9.3/8.9.3) with ESMTP id HAA95950 for ; Tue, 17 Aug 1999 07:12:13 -0400 (EDT) (envelope-from herouth@oumail.openu.ac.il) Received: from talmon.openu.ac.il (talmon.openu.ac.il [147.233.32.11]) by mx99.openu.ac.il (Postfix) with ESMTP for id 2044F4B5BF; Tue, 17 Aug 1999 14:12:12 +0300 (IDT) Received: from [147.233.159.109] (mac-herouth.pc.openu.ac.il) by talmon.openu.ac.il (Netscape Messaging Server 3.54) with ESMTP id AAA594B; Tue, 17 Aug 1999 14:15:49 +0300 X-Sender: herouth@shaked.cc.openu.ac.il Message-Id: In-Reply-To: <4.1.19990816164740.00c9fda0@mail.venux.net> References: <4.1.19990815225433.00cb6c20@mail.venux.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 17 Aug 1999 14:13:34 +0300 To: Matthew Hagerty , pgsql-sql@postgreSQL.org From: Herouth Maoz Subject: Re: [SQL] Stepping through a table. At 23:52 +0300 on 16/08/1999, Matthew Hagerty wrote: > > You mentioned that cursors are read only. Can I do update statements while > navigating with cursors? Or do they lock the records they are reading? If they do, they only lock them to other transactions. Since you are within the same connection and thus the same transaction (cursors can only be used within BEGIN/END transaction blocks), of course the records are not locked. As far as I know, you can make update statements. What I am not sure about is what happens if you rewind the cursor and read the updated record again - whether you will see the updated record or the non-updated one. You'll have to test this. Herouth -- Herouth Maoz, Internet developer. Open University of Israel - Telem project http://telem.openu.ac.il/~herutma