Re: Connections/Statements/ResultSets (Was: Re: Pooling

From: Curt Sampson <cjs(at)cynic(dot)net>
To: Thomas O'Dowd <tom(at)nooper(dot)com>
Cc: João Paulo Caldas Ribeiro <jp(at)mobicomp(dot)com>, Michael Paesold <mpaesold(at)gmx(dot)at>, <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: Connections/Statements/ResultSets (Was: Re: Pooling
Date: 2002-09-02 05:00:11
Message-ID: Pine.NEB.4.44.0209021359060.477-100000@angelic.cynic.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)cynic(dot)net> +81 90 7737 2974 http://www.netbsd.org
Don't you know, in this new Dark Age, we're all light. --XTC

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Th Templ 2002-09-02 11:53:43 Length of sql cols in postgresql
Previous Message Barry Lind 2002-09-02 03:15:50 Re: JDBC patch, so that bigint indexes get used