Received: from orion.SAPserv.Hamburg.dsh.de (Tpolaris2.sapham.debis.de [53.2.131.8]) by hub.org (8.9.3/8.9.1) with SMTP id DAA82831 for ; Mon, 26 Apr 1999 03:45:03 -0400 (EDT) (envelope-from wieck@sapserv.debis.de) Received: by orion.SAPserv.Hamburg.dsh.de for pgsql-sql@postgreSQL.org id m10bfrL-000EBZC; Mon, 26 Apr 99 09:31 MET DST Message-Id: From: jwieck@debis.com (Jan Wieck) Subject: Re: [SQL] PL/pgsql questions.. To: tveith@heaven.oeh.univie.ac.at Date: Mon, 26 Apr 1999 09:31:19 +0200 (MET DST) Cc: pgsql-sql@postgreSQL.org Reply-To: jwieck@debis.com (Jan Wieck) In-Reply-To: from "tveith@heaven.oeh.univie.ac.at" at Apr 25, 99 07:10:34 pm X-Mailer: ELM [version 2.4 PL25] Content-Type: text Thomas Veith wrote: > > One thing which I think is really important is PL/pgsql.. I carefully read > the bit of information which is available, but thats not very much.. Tnx > > I have 2 questions.. first, can you point me to some information about > this topic which i maybe have missed? Maybe you missed the docs in the programmers manual? > > second, take this procedure from an informix database: > > [...] > > so my question is, does PG/plsql support this, if so how, and if not, is > it planned to be supported in the near future? Functions in procedural languages (PL/Tcl, PL/pgSQL) inherit the same restrictions C language functions have in PostgreSQL. One of them I hate most is that they cannot return set results. Thus "RETURN ... AND RESUME" is currently not supported. It requires major changes to the function manager and executor. The time I expect it is not that near in future I would like it. Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #======================================== jwieck@debis.com (Jan Wieck) #