| From: | "Josh Berkus" <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Josh Berkus" <josh(at)agliodbs(dot)com> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Problems handling errors in PL/pgSQL |
| Date: | 2001-04-24 00:15:43 |
| Message-ID: | web-43243@davinci.ethosmedia.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
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: <unnamed> 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(at)agliodbs(dot)com
and data management solutions (415) 565-7293
for law firms, small businesses fax 621-2533
and non-profit organizations. San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-04-24 00:19:13 | Re: Problems handling errors in PL/pgSQL |
| Previous Message | Tom Lane | 2001-04-23 23:57:23 | Re: Problems handling errors in PL/pgSQL |