Shudnt' messages like
ERROR: value too long for type character varying(5)
Indicate which column and table the server is talking about .
Without that we need to open the application source code, find the
SQL, then describe the table to find which column is varchar(5)
and if there is two columns of varchar(5) we keep wondering.
similarly when uniq indexes are violated we do not know which
key is causing it.
MySQL is better in these small things.
I think in 7.4dev fkey violation are reported better,
cant such behaviours be extened to other kind of
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.
pgsql-general by date
|Next:||From: Tom Lane||Date: 2003-06-27 06:44:44|
|Subject: Re: Making pgsql error messages more developers' friendly. |
|Previous:||From: Tony Grant||Date: 2003-06-27 06:00:50|
|Subject: Re: How many fields in a table are too many|