Re: streaming result sets: progress

From: Nic Ferrier <nferrier(at)tapsellferrier(dot)co(dot)uk>
To: Thomas O'Dowd <tom(at)nooper(dot)com>
Cc: Barry Lind <blind(at)xythos(dot)com>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: streaming result sets: progress
Date: 2002-11-19 19:00:58
Message-ID: 87r8dhbd05.fsf@pooh-sticks-bridge.tapsellferrier.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Thomas O'Dowd <tom(at)nooper(dot)com> writes:

> > 3) I think the transaction characteristics of the current patch are just
> > fine and conform to the jdbc specification. The code should
> > automatically close the resultset when a commit occurs. One thing that
> > will be confusing is that noncursor based result sets will work accross
> > commits, but cursor based ones won't. But I think that is reasonable.
>
> Sounds reasonable to me as long as its clear to the programmer what type
> they are using. I definitely don't want to see the noncursor based
> resultsets closed, but I can't see a better solution for cursor based
> ones...

How can we make clear what type of ResultSet is being used?

Nic

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Paulo Eduardo Azevedo Silveira 2002-11-19 20:38:39 jdbc1 AbstractJdbc1Statement setObject() does not work with some Stream types
Previous Message Michael Stephenson 2002-11-19 17:38:50 Re: TEXT Data Type