Received: from smtp018.mail.yahoo.com (smtp018.mail.yahoo.com [216.136.174.115]) by postgresql.org (8.11.3/8.11.1) with SMTP id f6IAmXa21609 for ; Wed, 18 Jul 2001 06:48:33 -0400 (EDT) (envelope-from janwieck@yahoo.com) Received: from jupiter.us.greatbridge.com (65.196.69.55) by smtp.mail.vip.sc5.yahoo.com with SMTP; 18 Jul 2001 10:48:29 -0000 X-Apparently-From: Received: (from wieck@localhost) by jupiter.us.greatbridge.com (8.11.2/8.11.2) id f6IAsYd20969; Wed, 18 Jul 2001 06:54:34 -0400 From: Jan Wieck Message-Id: <200107181054.f6IAsYd20969@jupiter.us.greatbridge.com> Subject: Re: SPI_exec does not return! In-Reply-To: <3B55445B.36E16A4@imsd.uni-mainz.de> from Markus Wagner at "Jul 18, 2001 10:10:03 am" To: Markus Wagner Date: Wed, 18 Jul 2001 06:54:34 -0400 (EDT) CC: "pgsql-sql@postgresql.org" 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: 200107/243 X-Sequence-Number: 4039 Markus Wagner wrote: > Hi, > > if I do a SELECT on a non-existing table, SPI_exec won't return. > I get, e. g. in pgaccess, an error message " does not exist", > and my code below the function call is never reached. Right, the SPI_exec() call in turn calls the PostgreSQL parser and that raises an elog(ERROR) which longjmp()'s back into the backends main loop waiting for the next client query. > > So why return error codes for SPI_exec when you cannot evaluate them? What do you want here? No error, just an empty result of unspecified format? If the parser cannot determine (due to nonexistance of a table) which datatype the columns of the result set at least should have, what else could he do than trowing an ERROR? > > The background: > > I need to distinguish different client connections within a trigger > function. > To do this, I create a temporary table within a "login" function. > My trigger must check for the existence of this function. > I cannot think of any other method, since there is no "connection id" or > something like that! Unfortunately PL/pgSQL doesn't have global variables. PL/Tcl can have. If you cannot code a part of the login mechanism in PL/Tcl, setting a global variable and returning that in another PL/Tcl function, you could create a temp table with the same name in every connection and fill the connection-ID into that. Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== JanWieck@Yahoo.com # _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com