Re: Proposed patch for error locations - Mailing list pgsql-patches

From Michael Glaesemann
Subject Re: Proposed patch for error locations
Date
Msg-id C3817205-17E1-4D6C-9D92-ED6045123F92@myrealbox.com
Whole thread Raw
In response to Proposed patch for error locations  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Proposed patch for error locations  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches
On Mar 13, 2006, at 2:37 , Tom Lane wrote:

> to wit, that we make use of bison's "locations" feature to track token
> positions in the grammar, and add locations to raw parse tree nodes as
> needed.
>
> Some examples of what it can do:

This looks really nice.

> One thing I'm noticing already is that the addition of "at
> character N"
> to a lot of these messages isn't an improvement.  In psql it's
> certainly
> redundant with the error-cursor display.

The pure character count is definitely difficult to use with larger
queries. I think it could be more useful if it were
line:char_of_line. Would others find this useful?

Michael Glaesemann
grzm myrealbox com




pgsql-patches by date:

Previous
From: Neil Conway
Date:
Subject: Re: Fix syntax errors in contrib uninstall scripts
Next
From: ITAGAKI Takahiro
Date:
Subject: Re: [HACKERS] Automatic free space map filling