Re: plperl error format vs plpgsql error format vs pgTAP

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kevin Field <kevinjamesfield(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: plperl error format vs plpgsql error format vs pgTAP
Date: 2009-05-28 21:15:44
Message-ID: 441.1243545344@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Kevin Field <kevinjamesfield(at)gmail(dot)com> writes:
> I wanted to use the SQLSTATE code, but it's always XX000. If there
> were some way to set it when calling elog()

ereport?

http://developer.postgresql.org/pgdocs/postgres/error-message-reporting.html

At the plpgsql level, since 8.4 you can specify a SQLSTATE in RAISE.
AFAIR nobody's gotten round to doing anything about it in plperl.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David E. Wheeler 2009-05-28 21:18:12 Re: plperl error format vs plpgsql error format vs pgTAP
Previous Message Aidan Van Dyk 2009-05-28 20:56:56 Re: PostgreSQL Developer meeting minutes up