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

From Kevin Field
Subject Re: plperl error format vs plpgsql error format vs pgTAP
Date
Msg-id 2fc8fb45-a27c-4497-b082-cb56b80c9d49@g20g2000vba.googlegroups.com
Whole thread Raw
In response to plperl error format vs plpgsql error format vs pgTAP  (Kevin Field <kevinjamesfield@gmail.com>)
Responses Re: plperl error format vs plpgsql error format vs pgTAP  (Robert Haas <robertmhaas@gmail.com>)
Re: plperl error format vs plpgsql error format vs pgTAP  (Andrew Dunstan <andrew@dunslane.net>)
Re: plperl error format vs plpgsql error format vs pgTAP  ("David E. Wheeler" <david@kineticode.com>)
List pgsql-hackers
On May 28, 5:19 pm, da...@kineticode.com ("David E. Wheeler") wrote:
> On May 28, 2009, at 12:53 PM, Kevin Field wrote:
>
> >> Can pgTap check for a regex instead if just a string?
>
> > That's the other option, if the pgTAP author is willing...if the
> > SQLSTATE thing doesn't work out I guess we'll have to go down that
> > road.
>
> Patches welcome. ;-)
>
>    http://github.com/theory/pgtap/tree/master/
>
> I'm getting a new version ready to release as I type.

Thanks, great to know.  :)  Although, I do think changing plperl is
the more proper option, so I'm going to try there first...


pgsql-hackers by date:

Previous
From: "Markus Wanner"
Date:
Subject: Re: PostgreSQL Developer meeting minutes up
Next
From: Tom Lane
Date:
Subject: Re: pg_migrator and an 8.3-compatible tsvector data type