| From: | "David Wall" <d(dot)wall(at)computer(dot)org> |
|---|---|
| To: | "Max Khon" <fjoe(at)iclub(dot)nsu(dot)ru>, "Peter Mount" <peter(at)retep(dot)org(dot)uk> |
| Cc: | <pgsql-interfaces(at)postgresql(dot)org> |
| Subject: | Re: JDBC error codes to detect duplicates? |
| Date: | 2001-03-01 22:08:47 |
| Message-ID: | 003701c0a29c$304b1a00$5a2b7ad8@expertrade.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
> >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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2001-03-01 22:54:55 | Re: JDBC error codes to detect duplicates? |
| Previous Message | Peter Mount | 2001-03-01 21:28:36 | Re: JDBC error codes to detect duplicates? |