Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!fu-berlin.de!uni-berlin.de!not-for-mail
From: "M. Strobel" <sorry_no_mail_here@nowhere.dee>
Newsgroups: comp.databases.postgresql
Subject: Re: SQL state /
Date: Sat, 30 Apr 2011 18:00:34 +0200
Lines: 17
Message-ID: <922q12Fcr5U2@mid.uni-berlin.de>
References: <be953af4-d251-4de9-b405-f5bc7b44c11c@hg8g2000vbb.googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Trace: news.uni-berlin.de msLIL0VtJYUCZBBwFB2UBwoBz+kl+t3zFBZecYpOCgqXDYo9c=
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6
In-Reply-To: <be953af4-d251-4de9-b405-f5bc7b44c11c@hg8g2000vbb.googlegroups.com>
Xref: x330-a1.tempe.blueboxinc.net comp.databases.postgresql:105

Am 26.04.2011 15:28, schrieb Dog is love:
> Hi,
> 
> I was trying to trap the SQL States as listed in
> 
>   http://www.postgresql.org/docs/8.2/static/errcodes-appendix.html
> 
> in a normal pg/plsql script but I can't seem to do it....is it only
> possible to do this in Embedded SQL ?
> 
> I do not want to test the error code, I only want to pass it back to a
> JAVA front end.

I can tell you I can't trap any errors in pltcl, the error is
reflected to the client.

/Str.