Re: Making pgsql error messages more developers' friendly.

On Friday 27 Jun 2003 12:14 pm, Tom Lane wrote:
> Rajesh Kumar Mallah <mallah(at)trade-india(dot)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 ;-)
>

I wish i could ;-)

> 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...)

Thanks for explaining.
PostgreSQL already exceeds our expectations in the things
which really matters.

>
> regards, tom lane

--
Rajesh Kumar Mallah,
Project Manager (Development)
Infocom Network Limited, New Delhi
phone: +91(11)6152172 (221) (L) ,9811255597 (M)

Visit http://www.trade-india.com ,
India's Leading B2B eMarketplace.