Re: Patch for Improved Syntax Error Reporting - Mailing list pgsql-patches

From Bruce Momjian
Subject Re: Patch for Improved Syntax Error Reporting
Date
Msg-id 200108022159.f72LxP024931@candle.pha.pa.us
Whole thread Raw
In response to Re: Patch for Improved Syntax Error Reporting  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Patch for Improved Syntax Error Reporting
List pgsql-patches
> Maybe I'm confused, but I don't think any of the proposals would require
> you to do any of those things.  The only case that requires any
> significant new effort from the client app is where it reformats queries
> before sending them on to the parser ... but that is knowledge you've
> already built into the client, no?  You just have to remember what you
> did so that you can map a backend error index into the original text.

That seems particularly hard.  If you collapse spaces and stuff, it is
hard to figure out how it was originally formatted.  I would just return
the collapsed version locating the error.

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: Revised Patch to allow multiple table locks in "Unison"
Next
From: Dave Page
Date:
Subject: RE: Patch for Improved Syntax Error Reporting