>> It is sad for users the only way to distinguish the conditions is by >> looking at the error messages. They want to know the root of the >> problem. > > Sure. It's always a balance. If you go to the extreme of your argument > every possible error gets one individual error code. But then error > handling gets too complex.
I think the solution for this is assigning a unique id to each message. This is already done in some commercial databases. They are pretty usefull for tech supports. Best regards, -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese:http://www.sraoss.co.jp -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
