Re: plperl error format vs plpgsql error format vs pgTAP - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: plperl error format vs plpgsql error format vs pgTAP
Date
Msg-id 0739180E-7418-465F-9263-1F16C346B6F4@kineticode.com
Whole thread Raw
In response to Re: plperl error format vs plpgsql error format vs pgTAP  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On May 28, 2009, at 12:22 PM, Tom Lane wrote:

> What you need is a test that looks at the SQLSTATE code, and little
> if anything else.

Yes, and throws_ok() supports that:
    SELECT throws_ok( 'SELECT 1 / 0', '22012' );

Best,

David


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: plperl error format vs plpgsql error format vs pgTAP
Next
From: "David E. Wheeler"
Date:
Subject: Re: plperl error format vs plpgsql error format vs pgTAP