| From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | pg(at)fastcrypt(dot)com, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: JDBC gripe list |
| Date: | 2011-03-27 14:15:18 |
| Message-ID: | AANLkTi=MMJk-8R38V2RGYKuqwZCeFZfA1fzM8bwKeBGd@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On 28 March 2011 02:31, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> 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?
Or something else?
Oliver
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2011-03-27 15:14:38 | Re: JDBC gripe list |
| Previous Message | Oliver Jowett | 2011-03-27 14:10:07 | Re: idea to have driver return immediately after a query |