Re: setFetchSize() bug?
От | Felipe Schnack |
---|---|
Тема | Re: setFetchSize() bug? |
Дата | |
Msg-id | 20030804162912.327c073f.felipes@ritterdosreis.br обсуждение исходный текст |
Ответ на | setFetchSize() bug? (Felipe Schnack <felipes@ritterdosreis.br>) |
Список | pgsql-jdbc |
That's not the problem, I'm already with autocommit set to false... the problem is elsewhere. I believe it's on serverside prepared statements (or the lack of it) use. On 04 Aug 2003 15:24:26 -0400 Kim Ho <kho@redhat.com> wrote: > Hi, > > You might want to do a > con.setAutoCommit(false); > to force it to use cursors. > > > As you put it, the driver is probably not using server side prepared > statements or cursors. > > Cheers, > > Kim > > On Mon, 2003-08-04 at 11:18, 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) > -- > Kim Ho <kho@redhat.com> > -- /~\ The ASCII Felipe Schnack (felipes@ritterdosreis.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@ritterdosreis.br Fone: 51-32303341
В списке pgsql-jdbc по дате отправления: