Received: from orion.SAPserv.Hamburg.dsh.de (Tpolaris2.sapham.debis.de [53.2.131.8]) by hub.org (8.9.3/8.9.3) with SMTP id EAA25006 for ; Sun, 9 Apr 2000 04:05:24 -0400 (EDT) (envelope-from wieck@debis.com) Received: by orion.SAPserv.Hamburg.dsh.de for pgsql-sql@postgresql.org id m12eCbV-0003kyC; Sun, 9 Apr 100 09:57 MET DST Message-Id: From: wieck@debis.com (Jan Wieck) Subject: Re: PL/pgSQL & Cursors In-Reply-To: <0C95935DA0D5D3118E9800A0C9824CD02B8A19@mail.xperts.com> from "Dwelle, Timothy" at "Apr 7, 2000 10:46:57 am" To: "Dwelle, Timothy" Date: Sun, 9 Apr 2000 09:57:57 +0200 (CEST) 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-Archive-Number: 200004/84 [Charset iso-8859-1 unsupported, filtering to ASCII...] > I have been playing around with the PL/pgSQL stuff, and I have > been having trouble getting cursors to work inside my PL/pgSQL > functions. Reading through the documentation, I see that: > > (1) cursors must occur inside a transaction, and > (2) PL/pgSQL functions cannot start or end a transaction Maybe it's only the parser of PL/pgSQL. But AFAIK there are also problems with using named portals over SPI (what a cursor is). There are other things I want to do on PL/pgSQL after 7.0 is out. So I'll give it a try then. Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #========================================= wieck@debis.com (Jan Wieck) #