From: | Kris Jurka <books(at)ejurka(dot)com> |
---|---|
To: | Guillaume Cottenceau <gc(at)mnc(dot)ch> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: NPE sent by driver when ResultSet's connection is closed, |
Date: | 2004-12-17 21:36:44 |
Message-ID: | Pine.BSO.4.56.0412171627040.29231@leary.csoft.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Fri, 17 Dec 2004, Guillaume Cottenceau wrote:
> I am having some trouble with java.sql.ResultSet being "closed"
> when it should not in our application, and it has shown what is I
> think a bug in the driver.
>
> When the ResultSet is "closed", and I fire #next, I receive an
> SQLException complaining that the connection is closed. But when
> I fire #first, I receive a NullPointerException from driver code,
> which is incorrect since java.sql.ResultSet states that #first
> only throws SQLException.
Well, no one really declares throwing NPE because it's a RuntimeException,
but yes this is a bug and has been on the todo list for a while. Your
complaint has motivated me to do this and I've committed a hopefully
complete fix to this whole class of problems to the cvs repository.
Kris Jurka
From | Date | Subject | |
---|---|---|---|
Next Message | Kris Jurka | 2004-12-17 21:37:10 | Re: Updated french translation |
Previous Message | Guillaume Cottenceau | 2004-12-17 09:43:29 | NPE sent by driver when ResultSet's connection is closed, proposed patch |