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

Re: [Erserver-general] Why does Statement.close() close result

From: Oliver Jowett <oliver(at)opencloud(dot)com>
To: Barry Lind <blind(at)xythos(dot)com>
Cc: Jan Wieck <JanWieck(at)Yahoo(dot)com>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: [Erserver-general] Why does Statement.close() close result
Date: 2003-10-15 04:21:48
Message-ID: 20031015042146.GD30784@opencloud.com (view raw or flat)
Thread:
Lists: pgsql-jdbc
(cc: list trimmed)

On Tue, Oct 14, 2003 at 06:08:02PM -0700, Barry Lind wrote:

> Most of these methods are currently not implemented by the jdbc driver 
> however.  And further more the nature of the methods are such that they 
> envision the 'holdability' setting to be one set at the Connection 
> level, as opposed to something that might vary from ResultSet to 
> ResultSet as it would need to in our current implementation.

Actually you can specify holdability per statement, much like resultset type
and concurrency -- see:

  http://java.sun.com/j2se/1.4.2/docs/api/java/sql/Connection.html#createStatement(int,%20int,%20int)

-O

In response to

pgsql-jdbc by date

Next:From: Jan WieckDate: 2003-10-15 12:24:19
Subject: Re: [Erserver-general] Why does Statement.close() close result
Previous:From: Barry LindDate: 2003-10-15 01:08:02
Subject: Re: [Erserver-general] Why does Statement.close() close result

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