Re: JDBC gripe list

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <oliver(at)opencloud(dot)com>
Cc: <pg(at)fastcrypt(dot)com>,<pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: JDBC gripe list
Date: 2011-03-27 16:37:26
Message-ID: 4D8F2176020000250003BCB7@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

> Oliver Jowett wrote:
> Kevin Grittner wrote:
>> Dave Cramer wrote:
>>
>>> My sense is that for basic read/write/update/delete the driver
>>> works just fine. However I'd like to compile a list of everyone's
>>> gripe.
>>
>> At the top of my list is the need to use a cursor to avoid
>> materializing the entire result set in heap during execution of an
>> execute method. Pulling data off the wire should be done in
>> ResultSet.next() method.
>
> Do you mean something beyond the batching you can do by setting a
> suitable fetchsize?
> Or do you mean you want to lift the restrictions on when that
> batching can actually be used?

I'm talking about doing this even when a cursor isn't used, no
fetchSize is set, and without the restrictions (like autoCommit being
off and the query string being a single statement). Unfortunately I
didn't see the other thread on this topic before I responded to this
thread, so we should probably let the point die on this thread.

-Kevin

Browse pgsql-jdbc by date

  From Date Subject
Next Message Kevin Grittner 2011-03-27 16:46:08 Re: idea to have driver return immediately after a query
Previous Message Thomas Kellerer 2011-03-27 15:19:45 Re: JDBC gripe list