Re: Patch for more readable parse error messages

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Jeroen van Vianen <jeroen(at)design(dot)nl>, pgsql-patches(at)postgresql(dot)org
Subject: Re: Patch for more readable parse error messages
Date: 2000-06-09 15:18:04
Message-ID: 18988.960563884@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Can someone remind me where we are on this. I seem to remember we have
> to have db clients report the location because of problems with
> interfaces handling the error output.

I think we rejected that form of the patch. ISTM the right answer is
for the backend to hand back some fairly machine-friendly indication
of the error position (character NNN, probably) and let the frontend
decide how it wants to make use of the info. This ought to be done
in conjunction with the other changes in error reporting methods that
people have been muttering about --- supply identifiable error codes,
separate location-in-backend-code information from the error itself,
etc etc.

regards, tom lane

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2000-06-09 15:26:40 Re: BeOS take 2
Previous Message Tom Lane 2000-06-09 15:05:21 Re: Re: [CORE] Re: MY PATCH