setFetchSize() bug?

From: Felipe Schnack <felipes(at)ritterdosreis(dot)br>
To: pgsql-jdbc <pgsql-jdbc(at)postgresql(dot)org>
Subject: setFetchSize() bug?
Date: 2003-08-04 15:18:08
Message-ID: 20030804121808.65088c1d.felipes@ritterdosreis.br
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

I just found something about the way setFetchSize() is implemented in current CVS version of the driver, I'm wondering if it's a bug, probably it is. I just found that if you don't use server-side preparedstatements, the following exception is thrown (I sent this same exception earlier today). This is a bug? I can't understand it very well.... seems to me that the driver uses the statement's name as the cursor name??

java.sql.SQLException: ERROR: parser: parse error at or near "null" at character 23
at org.postgresql.core.QueryExecutor.executeV2(QueryExecutor.java:286)
at org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:104)
at org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:66)
at org.postgresql.jdbc1.AbstractJdbc1ResultSet.next(AbstractJdbc1ResultSet.java:135)
at org.apache.commons.dbcp.DelegatingResultSet.next(DelegatingResultSet.java:135)

--

/~\ The ASCII Felipe Schnack (felipes(at)ritterdosreis(dot)br)
\ / Ribbon Campaign Analista de Sistemas
X Against HTML Cel.: 51-91287530
/ \ Email! Linux Counter #281893

Centro Universitário Ritter dos Reis
http://www.ritterdosreis.br
ritter(at)ritterdosreis(dot)br
Fone: 51-32303341

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message David Wall 2003-08-04 15:40:41 Re: Server side resultset search (for performance reasons)
Previous Message Jesus Sandoval 2003-08-04 14:23:35 Re: Server side resultset search (for performance reasons)