On Fri, May 29, 2009 at 7:59 AM, Kevin Field <kevinjamesfield(at)gmail(dot)com> wrote:
> On May 28, 5:19 pm, da(dot)(dot)(dot)(at)kineticode(dot)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. ;-)
>> 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...
It seems to me that removing line numbers from PL/perl error messages
is not a good solution to anything. Line numbers are extremely useful
for debugging purposes, and getting rid of them because one particular
testing framework doesn't know how to use regular expressions is
solving the wrong problem.
I'm also a bit confused because your original post had a line number
in the PL/pgsql output, too, just formatted slightly differently. Why
doesn't that one cause a problem?
In response to
pgsql-hackers by date
|Next:||From: Andrew Dunstan||Date: 2009-05-29 15:37:59|
|Subject: Re: plperl error format vs plpgsql error format vs pgTAP|
|Previous:||From: Aidan Van Dyk||Date: 2009-05-29 15:34:35|
|Subject: Re: PostgreSQL Developer meeting minutes up|