Re: Connections/Statements/ResultSets (Was: Re: Pooling - Mailing list pgsql-jdbc

From Curt Sampson
Subject Re: Connections/Statements/ResultSets (Was: Re: Pooling
Date
Msg-id Pine.NEB.4.44.0209021359060.477-100000@angelic.cynic.net
Whole thread Raw
In response to Re: Connections/Statements/ResultSets (Was: Re: Pooling  (Thomas O'Dowd <tom@nooper.com>)
List pgsql-jdbc
On 31 Aug 2002, Thomas O'Dowd wrote:

> In either case, it would be nice to have a nice big red flag waved on
> the list if the multiple ResultSet thing is going to go away. It will
> definitely break a lot of my code and I'm not so sure its so wrong.

It's not wrong, but it's not at all portable to assume that you
can have more than one active ResultSet on a connection. So you
may want to change your habit anyway, unless you're sure you'll
never have to use another database.

cjs
--
Curt Sampson  <cjs@cynic.net>   +81 90 7737 2974   http://www.netbsd.org
    Don't you know, in this new Dark Age, we're all light.  --XTC


pgsql-jdbc by date:

Previous
From: Barry Lind
Date:
Subject: Re: JDBC patch, so that bigint indexes get used
Next
From: "Th Templ"
Date:
Subject: Length of sql cols in postgresql