From: | Rene Pijlman <rpijlman(at)wanadoo(dot)nl> |
---|---|
To: | Peter Wiley <wiley(at)mmspl(dot)com(dot)au> |
Cc: | "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: JDBC changes for 7.2 - wish list item |
Date: | 2001-08-27 18:01:18 |
Message-ID: | qd2lot8717rdm9prbhmsinh9ehsno0brp4@4ax.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-jdbc |
On Mon, 27 Aug 2001 08:48:52 +1000 (EST), you wrote:
>It's been mentioned before, but a set of error numbers for database errors
>would make trapping exceptions and dealing with them gracefully a LOT
>simpler. I have java code that runs against Oracle, Informix, PostgreSQL,
>MS SQL Server and Cloudscape. All(?) the others have an error code as well
>as an error message and it's a lot easier to get the error code.
I agree. Its on the list on
http://lab.applinet.nl/postgresql-jdbc/#SQLException. This
requires new functionality in the backend.
>Of course, they all have *different* error codes for the same error (ie
>primary key violation). Nothing is ever simple.
Perhaps the SQLState string in SQLException can make this easier
(if we can support this with PostgreSQL). This is supposed to
contain a string identifying the exception, following the Open
Group SQLState conventions. I'm not sure how useful these are.
Regards,
René Pijlman
From | Date | Subject | |
---|---|---|---|
Next Message | Frank Joerdens | 2001-08-27 18:08:25 | Re: Toast,bytea, Text -blob all confusing |
Previous Message | Carfield Yim | 2001-08-27 17:31:57 | Where can I learn more about Multi-Version Concurrency Control? |
From | Date | Subject | |
---|---|---|---|
Next Message | Barry Lind | 2001-08-27 18:07:55 | Re: Proposal to fix Statement.executeBatch() |
Previous Message | chris markiewicz | 2001-08-27 17:54:59 | RE: Fastpath error on solaris 2.8 pgsql 7.1.3 |