From: | "Brendan Jurd" <direvus(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Attaching error cursor position to invalid constant values |
Date: | 2008-08-31 00:50:16 |
Message-ID: | 37ed240d0808301750s5c1e98a8gb968d70446a9dd22@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Aug 31, 2008 at 6:18 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | KaiGai Kohei | 2008-08-31 03:41:40 | Proposal of SE-PostgreSQL patches (for CommitFest:Sep) |
Previous Message | David Rowley | 2008-08-31 00:18:26 | TODO item: Implement Boyer-Moore searching (First time hacker) |