Re: Making pgsql error messages more developers' friendly. - Mailing list pgsql-general

From Tom Lane
Subject Re: Making pgsql error messages more developers' friendly.
Date
Msg-id 25418.1056696284@sss.pgh.pa.us
Whole thread Raw
In response to Making pgsql error messages more developers' friendly.  (Rajesh Kumar Mallah <mallah@trade-india.com>)
Responses Re: Making pgsql error messages more developers' friendly.  (Rajesh Kumar Mallah <mallah@trade-india.com>)
List pgsql-general
Rajesh Kumar Mallah <mallah@trade-india.com> writes:
> Shudnt'  messages like
> ERROR:  value too long for type character varying(5)
> Indicate which column and table the server is talking about .

Send a patch ;-)

This is not that easy to do: the code that implements the constraint
does not know what it is being applied to.  In the general case it
cannot know, because there may be no specific table/column it's being
applied to --- consider "SELECT 'foobar'::char(5)".  But if you have
an idea how to give a more-specific error message when possible,
let's see some code.

(Possible plan: the recently-added error context mechanism might
be able to do something for this...)

            regards, tom lane

pgsql-general by date:

Previous
From: Rajesh Kumar Mallah
Date:
Subject: Making pgsql error messages more developers' friendly.
Next
From: "Nigel J. Andrews"
Date:
Subject: Re: Making pgsql error messages more developers' friendly.