Re: Proposed p.tch for error locations - Mailing list pgsql-interfaces

From Alvaro Herrera
Subject Re: Proposed p.tch for error locations
Date
Msg-id 20060313153209.GA15002@surnet.cl
Whole thread Raw
In response to Re: [PATCHES] Proposed patch for error locations  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Proposed p.tch for error locations
Re: [PATCHES] Proposed p.tch for error locations
List pgsql-interfaces
Tom Lane wrote:

> The change in behavior would actually be in libpq, because it's
> PQerrorMessage that is doing the deed (assuming a reasonably modern
> server and libpq).  What I was considering proposing was that we migrate
> the error-cursor feature out of psql and into PQerrorMessage.  This
> would mean that you'd get responses like
>
> ERROR:  column "foo" does not exist
> LINE 1: select foo from a;
>                ^

This doesn't work on terminal using a variable-width font, does it?
Sure, you can have all the interfaces use a monospace font, but it seems
a weird thing to do.  I think the line/character position should be
returned in a separate error attribute in ereport.  So for example
pgAdmin could count characters and mark it in bold or use a different
color.

--
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

pgsql-interfaces by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCHES] Proposed patch for error locations
Next
From: Tom Lane
Date:
Subject: Re: Proposed p.tch for error locations