Skip site navigation (1) Skip section navigation (2)

Re: JDBC changes for 7.2 - wish list item

From: Barry Lind <barry(at)xythos(dot)com>
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 16:29:58
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-jdbc
This is on the TODO list for the backend.  As a post a couple of days 
ago stated, when the backend has error code support, it will also be 
added to JDBC.  Until then....


Peter Wiley 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.
> Of course, they all have *different* error codes for the same error (ie
> primary key violation). Nothing is ever simple.
> Peter Wiley
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?

In response to

pgsql-hackers by date

Next:From: Carfield YimDate: 2001-08-27 17:31:57
Subject: Where can I learn more about Multi-Version Concurrency Control?
Previous:From: Zeugswetter Andreas SB SDDate: 2001-08-27 15:25:43
Subject: RE: extern + static issue in datetime.c

pgsql-jdbc by date

Next:From: David DaneyDate: 2001-08-27 17:18:42
Subject: Re: [JDBC] Re: Bug #428: Another security issue with the JDBC driver.
Previous:From: T.R.MissnerDate: 2001-08-27 15:50:58
Subject: Fastpath error on solaris 2.8 pgsql 7.1.3

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group