Re: Attaching error cursor position to invalid constant values - Mailing list pgsql-hackers

From Brendan Jurd
Subject Re: Attaching error cursor position to invalid constant values
Date
Msg-id 37ed240d0808301750s5c1e98a8gb968d70446a9dd22@mail.gmail.com
Whole thread Raw
In response to Attaching error cursor position to invalid constant values  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Attaching error cursor position to invalid constant values  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-hackers
On Sun, Aug 31, 2008 at 6:18 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I'm fooling around with getting the parser to report an error cursor
> location if input conversion fails for a constant in a SQL command.
...
>
> This seems like it'd be a pretty useful thing to have in long queries,
> but in short queries it looks a bit like overkill.  And it affects
> the expected output of a whole lot of the regression tests.
>

This is a cool idea, but as you say it's pretty pointless for one-liner queries.

What about implementing some kind of cutoff point for query length.
As in, "Display the cursor if the query is < $whatever characters
long"?  I'm thinking most regression test queries would fall well
below a reasonable value of $whatever.

Cheers,
BJ


pgsql-hackers by date:

Previous
From: "David Rowley"
Date:
Subject: TODO item: Implement Boyer-Moore searching (First time hacker)
Next
From: Gregory Stark
Date:
Subject: Re: Attaching error cursor position to invalid constant values