Re: setFetchSize() bug?

There isn't enough information to debug this in the stack trace.  This
code seems fine and is there for some time already.

Do you have a small example that could be used to reproduce the problem?
  It would make it easier for us to track it down.

Regards,
Fernando

Felipe Schnack wrote:
>   I just found something about the way setFetchSize() is implemented in current CVS version of the driver, I'm
wonderingif it's a bug, probably it is. I just found that if you don't use server-side preparedstatements, the
followingexception 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)
>
>


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