| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 2003-10-15 12:24:19 | Re: [Erserver-general] Why does Statement.close() close result |
| Previous Message | Barry Lind | 2003-10-15 01:08:02 | Re: [Erserver-general] Why does Statement.close() close result |