Re: JVM & JDBC Upgrade --- Help !!

From: "Craig Golby" <craig(dot)golby(at)dignitas(dot)ltd(dot)uk>
To: "'Oliver Jowett'" <oliver(at)opencloud(dot)com>
Cc: <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: JVM & JDBC Upgrade --- Help !!
Date: 2011-09-25 23:16:14
Message-ID: 000301cc7bd9$1fe87730$5fb96590$@golby@dignitas.ltd.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Hi Oliver, a little research later and it does appear to be the case that
getFetchSize used to return the size of the resultset, but now doesn’t.

We were looking to upgrade Apache, Tomcat, PostgreSQL DRivers and ultimately
PostgreSQL itself, but in all honesty to change all the instances of this to
work in some other way would be a major undertaking for the application
developers.

As such, we will likely continue with what we have, as simply put, it works
!!

Thanks for your input.

Craig

-----Original Message-----
From: pgsql-jdbc-owner(at)postgresql(dot)org
[mailto:pgsql-jdbc-owner(at)postgresql(dot)org] On Behalf Of Oliver Jowett
Sent: 23 September 2011 00:42
To: craig(dot)golby(at)dignitas(dot)ltd(dot)uk
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: [JDBC] JVM & JDBC Upgrade --- Help !!

On 23 September 2011 11:16, Craig Golby <craig(dot)golby(at)dignitas(dot)ltd(dot)uk> wrote:

>         int rowCount = rsID.getFetchSize();

Well, there's your problem, getFetchSize() doesn't return the number
of rows in a resultset, it returns whatever fetch size is in use,
which defaults to 0.
(That's probably something that has changed since the 7.3 driver - the
7.3 driver did do some odd nonstandard things in that area, and if you
relied on them then yes your code will break)

Oliver

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Mike Fowler 2011-09-26 13:17:09 Buildfarm error: Broken compatability with JDK 1.4
Previous Message Craig Ringer 2011-09-25 11:53:57 Re: use of savepoint in containter managed transaction