From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
---|---|
To: | David Wall <d(dot)wall(at)computer(dot)org> |
Cc: | pgsql-jdbc-list <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Detecting 'socket errors' - closing the Connection object |
Date: | 2003-07-23 00:36:59 |
Message-ID: | 20030723003658.GF31669@opencloud.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Tue, Jul 22, 2003 at 05:25:36PM -0700, David Wall wrote:
> > Have you looked at the ConnectionEventListener approach? I know that it's
> > not currently implemented in postgresql, but it should be easy enough to
> > add, and in theory this is the standard way of doing it.
>
> No, we're still using JDK 1.3.1. It's amazing how slowly our customers
> migrate to new JDKs, especially the Fortune 500 players. When 1.5 comes
> out, they'll no doubt let us look into 1.4.
>
> Also, this is an entire new set of javax.sql classes that are not used in
> our application, so there are more issues for us when that time comes...
You can get at javax.sql under 1.3 (or probably even 1.2), it's just not
there as a standard package; pre-1.4 it was part of the "EE" sql addons.
Look for a "JDBC2 optional extensions" download somewhere on
java.sun.com.
(and then you get to rewrite all your app code to use Datasources! so much
for that plan.)
-O
From | Date | Subject | |
---|---|---|---|
Next Message | Kris Jurka | 2003-07-23 02:31:33 | Re: RFC: Removal of support for JDBC1 drivers. |
Previous Message | David Wall | 2003-07-23 00:25:36 | Re: Detecting 'socket errors' - closing the Connection object |