Re: Syntax decisions for pl/pgsql RAISE extension - Mailing list pgsql-hackers

From Zeugswetter Andreas OSB sIT
Subject Re: Syntax decisions for pl/pgsql RAISE extension
Date
Msg-id E1539E0ED7043848906A8FF995BDA579031CD9EE@m0143.s-mxs.net
Whole thread Raw
In response to Re: Syntax decisions for pl/pgsql RAISE extension  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Syntax decisions for pl/pgsql RAISE extension  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> So right now I'm thinking I like my original proposal
> http://archives.postgresql.org/pgsql-hackers/2008-05/msg00357.php
> with the exception that we should go with
>     SQLSTATE 'xyzzy'
> as the syntax in EXCEPTION lists.  Also I'm willing to go with
> ERRCODE rather than CODE as the name of the USING option, since

Other db's go with SQLCODE and SQLSTATE.
Would SQLCODE be better than ERRCODE ?

SQLCODE is usually an integer value, but the values correspond to
the strings used in pg. (Think of the strings as typedefs for a number,
like DEVIDE_BY_ZERO == -11028 SQLSTATE '22012')

Andreas


pgsql-hackers by date:

Previous
From: "Josh Tolley"
Date:
Subject: Re: Problem returning strings with pgsql 8.3.x
Next
From: "ranjit singh"
Date:
Subject: how to perform silent installation on linux and solaris