Re: setFetchSize() bug

From: Fernando Nasser <fnasser(at)redhat(dot)com>
To: Felipe Schnack <felipes(at)ritterdosreis(dot)br>
Cc: pgsql-jdbc <pgsql-jdbc(at)postgresql(dot)org>, Kim Ho <kho(at)redhat(dot)com>, Barry Lind <blind(at)xythos(dot)com>
Subject: Re: setFetchSize() bug
Date: 2003-08-05 21:46:44
Message-ID: 3F3025C4.5020209@redhat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Hi Felipe,

Your SQL DDL does not match your patch.

Nevertheless, I was able to reproduce your problem and tested Kim's
solution with the attached patch. It indeed solves the problem.

We will try and make a test case based on your example.
Thanks for sending it.

Regards,
Fernando

Felipe Schnack wrote:
> Hi all
> I just wrote the test case for the setFetchSize() bug I found these days. Attached to this message you get the Java source. The database I'm querying is defined in the following SQL fragment. Note you have to populate the table with data, as the error ocurrs when you call ResultSet.next()
>
> create table Auditoria (userIp varchar(15), codPessoa int , msgAudit varchar(200) not null, dataAudit timestamp default CURRENT_TIMESTAMP not null, tipoAudit int not null);
>
> Have fun :-)
>
>
>
> ------------------------------------------------------------------------
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org

--
Fernando Nasser
Red Hat Canada Ltd. E-Mail: fnasser(at)redhat(dot)com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9

Attachment Content-Type Size
CURSOR.PATCH text/plain 1.5 KB

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Fernando Nasser 2003-08-05 21:55:03 Re: Connection.setCatalog method
Previous Message Barry Lind 2003-08-05 21:34:26 Re: Connection.setCatalog method