Re: PostgreSQL, WebObjects and fetchSize

From: David Teran <david(dot)teran(at)cluster9(dot)com>
To: Kris Jurka <books(at)ejurka(dot)com>
Cc: pgsql-jdbc(at)postgresql(dot)org, Jan Willem Luiten <jwl(at)secondmove(dot)com>, Oliver Jowett <oliver(at)opencloud(dot)com>
Subject: Re: PostgreSQL, WebObjects and fetchSize
Date: 2005-05-12 09:21:12
Message-ID: 4f1469e0f88bdea906530297905bb55d@cluster9.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Scott Marlowe 2005-05-12 15:14:38 Re: Using PgSQL in high volume and throughput problem
Previous Message Nikola Milutinovic 2005-05-12 05:34:42 Using PgSQL in high volume and throughput problem