From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | David Wall <d(dot)wall(at)computer(dot)org> |
Cc: | Max Khon <fjoe(at)iclub(dot)nsu(dot)ru>, Peter Mount <peter(at)retep(dot)org(dot)uk>, pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: JDBC error codes to detect duplicates? |
Date: | 2001-03-01 22:54:55 |
Message-ID: | 200103012254.RAA25630@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
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(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
From | Date | Subject | |
---|---|---|---|
Next Message | Cedar Cox | 2001-03-02 08:56:21 | Re: JDBC error codes to detect duplicates? |
Previous Message | David Wall | 2001-03-01 22:08:47 | Re: JDBC error codes to detect duplicates? |