When using Openbase in the exact same setup, the out-of-memory error
does not occur and the the results are batched properly. So somehow
the jdbc adaptor for Openbase is able to perform this "trick" in
combination with WebObjects, while the PostgreSQL jdbc adaptor is
not. Yet, WO has no special provisions to work in conjunction with
Besides that, on the TODO list it says under "Performance":
Allow scrollable ResultSets to not fetch all results in one batch.
Could this have to do with the problem I encountered?
On May 11, 2005, at 4:27 PM, Oliver Jowett wrote:
> Jan Willem Luiten wrote:
>> Thanks for the prompt reply. Unfortunately I've got no access to
>> Statement.setFetchSize() from within WebObjects. Is there any
>> other way
>> to solve this?
> This is up to WebObjects to support -- it's a standard JDBC mechanism.
> The driver doesn't give you another way to set it.
In response to
pgsql-jdbc by date
|Next:||From: Dave Cramer||Date: 2005-05-11 17:16:58|
|Subject: in out parameter patch|
|Previous:||From: Oliver Jowett||Date: 2005-05-11 14:27:33|
|Subject: Re: PostgreSQL, WebObjects and fetchSize|