Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f3O0Fl335503 for ; Mon, 23 Apr 2001 20:15:47 -0400 (EDT) (envelope-from josh@agliodbs.com) Received: from [209.10.40.250] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.4.1) with HTTP id 43243; Mon, 23 Apr 2001 17:15:43 -0700 From: "Josh Berkus" Subject: Re: Problems handling errors in PL/pgSQL To: Tom Lane , "Josh Berkus" Cc: pgsql-sql@postgresql.org X-Mailer: CommuniGate Pro Web Mailer v.3.4.1 Date: Mon, 23 Apr 2001 17:15:43 -0700 Message-ID: In-Reply-To: <24242.988070243@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Archive-Number: 200104/363 X-Sequence-Number: 2721 Tom, > This would clearly be a bug, but I cannot replicate the problem: > > regression=# SELECT fn_save_order_details (7703, '{34,29,40}','{TRUE, > TRUE, FALSE}'); > ERROR: referential integrity violation - key referenced > from order_details not found in orders > regression=# Always good to have you folks test something. This does appear to be a bug ... in KPSQL (the KDE GUI for PSQL), not in Postgres. When I run it through command-line PSQL, an error is returned; for some reason, KPSQL returns the return value for the function and no error. Grazie! -Josh Berkus ______AGLIO DATABASE SOLUTIONS___________________________ Josh Berkus Complete information technology josh@agliodbs.com and data management solutions (415) 565-7293 for law firms, small businesses fax 621-2533 and non-profit organizations. San Francisco