Re: PostgreSQL, WebObjects and fetchSize - Mailing list pgsql-jdbc

From David Teran
Subject Re: PostgreSQL, WebObjects and fetchSize
Date
Msg-id 4f1469e0f88bdea906530297905bb55d@cluster9.com
Whole thread Raw
In response to Re: PostgreSQL, WebObjects and fetchSize  (Kris Jurka <books@ejurka.com>)
List pgsql-jdbc
Hi,

>>> 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.
>>
>
> Well defaulting it to a nonzero value is a reasonable thing to do, we
> have
> just chosen not to for the pg driver because of possible performance
> problems specific to pg.  We could consider exposing it via a URL
> parameter.
>

That would be fine. What default value do you suggest? Project Wonder
for WebObjects has a postgres plugin for WebObjects and i already added
some features to the plugin so in the  meantime i would add this
reasonable default value to the plugin so people using the plugin and
postgres and webobjects are happy. All i need to know is a good default
value.

And WebObjects is not using autocommit=true for Postgres, it respects
the transaction capability from postgres and uses normal transactions.

regards, David


pgsql-jdbc by date:

Previous
From: Nikola Milutinovic
Date:
Subject: Using PgSQL in high volume and throughput problem
Next
From: Scott Marlowe
Date:
Subject: Re: Using PgSQL in high volume and throughput problem