Re: [HACKERS] Re: [PATCHES] Patch for more readable parse error messages

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Jeroen van Vianen <jeroen(at)design(dot)nl>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] Re: [PATCHES] Patch for more readable parse error messages
Date: 2000-02-24 23:50:24
Message-ID: 200002242350.SAA21853@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> In any case, I believe that the actual error message string should be
> assembled in the front-end. I'm not too fond of the idea of letting
> clients parse out the interesting parts of an error out of a blob of text.
>
> Comments? Anyone interested? This would be very dear to my heart so I'd be
> very willing to spend a lot of time on it.

Vadim strongly believes in error mesage numbers. We certainly should do
better, if only to print a code before the error code or something.

--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-02-24 23:57:50 Re: [SQL] how to create index on timestamp field in pre v7 database
Previous Message Peter Eisentraut 2000-02-24 23:39:15 Re: [HACKERS] Re: [BUGS] First experiences with Postgresql 7.0