From: Tomasz Myrta <jasiek@klaster.net>
To: Radu-Adrian Popescu <radu.popescu@aldratech.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Catching DML exceptions in PL/pgSQL
Date: Tue, 17 Jun 2003 11:44:36 +0200
Message-ID: <3EEEE304.1010106@klaster.net> (raw)
In-Reply-To: <5.2.1.1.0.20030617121526.02185a50@192.168.0.1>
References: <5.2.1.1.0.20030617121526.02185a50@192.168.0.1>
Dnia 2003-06-17 11:25, Użytkownik Radu-Adrian Popescu napisał:
> Hello all,
> (and sorry if this has been aswered before)
>
> Take this piece of code for example:
> .....................
> begin
> _res.code:=1;
> select id into iid from log where id=_id;
> if not found then begin
> _res.msg:=''insert'';
> *insert into log (log, data) values (_log, _data);
> if not found* then begin
> _res.msg:=_res.msg || '' error'';
> _res.code:=-1;
> end;
> end if;
> end;
> else begin
> .....................
> The thing is if _data (parameter) is null and table has a (data <> null)
> check, the insert would fail and abort the function before my "if not
> found" test.
>
> I'm porting a java app. from mssql to postgresql, and the java code
> relies on the stored procedure to always return it's status (in
> _res.code in this case).
>
> Is there anything I can do to make sure the function always returns _res ?
> Something along the lines of Oracle's exception handling, or the @@error
> trick in mssql ?
You can't do it this way. Your insert is violation of some constraint
(problably "not null" or "primary key" constraint). This kind of violation
raises exception and whole transaction is aborted. I don't use java, but C
librares raises also ordinary C exception which can be easily caught. If you
want to avoid such cases - check your data before inserting them.
Regards,
Tomasz Myrta
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: jasiek@klaster.net, radu.popescu@aldratech.com
Subject: Re: Catching DML exceptions in PL/pgSQL
In-Reply-To: <3EEEE304.1010106@klaster.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox