From: | Vincent Janelle <random(at)goblinstudios(dot)com> |
---|---|
To: | "Simpson, Mike W" <mike(dot)simpson(at)pbs(dot)proquest(dot)com> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Out of memory error on huge resultset |
Date: | 2002-10-11 21:53:19 |
Message-ID: | 20021011175319.68fc20c7.random@goblinstudios.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
But what if your data changes?
On Fri, 11 Oct 2002 15:49:42 -0600
"Simpson, Mike W" <mike(dot)simpson(at)pbs(dot)proquest(dot)com> wrote:
> This definitely isn't my field, but in our code we're perfectly happy
> setting LIMIT and OFFSET. In combination with stored procedures,
> performance is excellent.
>
> If you really want a driver change, wouldn't it be simpler to just append
> LIMIT and OFFSET?
> Anytime setFetchSize is called, just tack on
> query+=" LIMIT "+getFetchSize()+" OFFSET "+rowPointer;
> and rs.next()/cursor code increment the rowPointer.
>
> Just my 2 cents...
> Mike
>
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2002-10-11 22:18:47 | Re: Out of memory error on huge resultset |
Previous Message | Simpson, Mike W | 2002-10-11 21:49:42 | Re: Out of memory error on huge resultset |