| From: | Peter Wiley <wiley(at)mmspl(dot)com(dot)au> |
|---|---|
| To: | Ned Wolpert <ned(dot)wolpert(at)knowledgenet(dot)com> |
| Cc: | "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | JDBC changes for 7.2 - wish list item |
| Date: | 2001-08-26 22:48:52 |
| Message-ID: | Pine.LNX.4.33.0108270842310.22089-100000@rex.vpn.mmsi.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-jdbc |
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.
Of course, they all have *different* error codes for the same error (ie
primary key violation). Nothing is ever simple.
Peter Wiley
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-08-26 23:08:09 | Anyone see any value in LockDisable/LockingDisabled mechanism? |
| Previous Message | Peter Eisentraut | 2001-08-26 22:46:47 | Re: Re: [PATCHES] Makefile.PL for Pg.so |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | T.R.Missner | 2001-08-27 15:50:58 | Fastpath error on solaris 2.8 pgsql 7.1.3 |
| Previous Message | Anders Bengtsson | 2001-08-26 19:56:09 | Re: Status of JDBC test suite? |