As stated, the backend protocol doesn't pass error codes but error
messages. My question is, are there enough of these kind of things to
create a new protocol version (7.2)? After all, we are still using the
same protocol since (?)6.5. I think adding error codes would not only
benefit JDBC but ODBC and possibly others also. I know there have been
various discussions like this one about parsing error messages in the ODBC
driver. As I remember, there were one or two other things that have been
discussed that would require a change in the protocol also. Just my two
cents.
-Cedar
On Thu, 1 Mar 2001, Bruce Momjian wrote:
> I have ideas on how to do error codes and multiple languages. I can
> make a proposal for 7.2.
>
> [ Charset ISO-8859-1 unsupported, converting... ]
> > > >AFAIK clean implementation of such feature is not possible because
> > backend
> > > >protocol does not have error codes (only error messages)
> > >
> > > Thats correct. It's also not practical to get the driver to translate
> > > because the format of the messages can change between releases as well.
> >
> > Practically speaking, how often do the messages really change between
> > releases? It seems that we could create a pluggable translator that would
> > work based on the release version. If the messages change too frequently,
> > then something's seriously wrong with Postgresql server since the main
> > sql-portion of the system has been in place and there aren't too many things
> > a program really needs to detect about a database (missing row, duplicate
> > key, constraint violation, transaction error, deadlock detected, etc.).
> >
> > David
> >
> >
>
>
> --
> Bruce Momjian | http://candle.pha.pa.us
> pgman@candle.pha.pa.us | (610) 853-3000
> + If your life is a hard drive, | 830 Blythe Avenue
> + Christ can be your backup. | Drexel Hill, Pennsylvania 19026
>
