Re: setFetchSize question
От | Dave Smith |
---|---|
Тема | Re: setFetchSize question |
Дата | |
Msg-id | 1109348470.14394.43.camel@playpen.candata.com обсуждение исходный текст |
Ответ на | setFetchSize question (Alan Stange <stange@rentec.com>) |
Ответы |
Re: setFetchSize question
|
Список | pgsql-jdbc |
Funny, I'm trying to do the same thing. I think the problem is that V3 protocol (bind/execute) , Postgresql does not log the portal command just the SQL statement. I'm busy trying to find the link in the archives to this problem .. On Fri, 2005-02-25 at 11:12, Alan Stange wrote: > Hello all, > > I just noticed something and I thought I'd ask: > > When reading large chunks of data in the 7.4 JDBC client I would code > something like this: > > conn.setAutoCommit(false); > st.setFetchDirection(ResultSet.FETCH_FORWARD); > st.setFetchSize(1000); > st.executeQuery("select * from foo"); > > which would result in queries to the postgresql server like this: > > DECLARE JDBC_CURS_588 CURSOR FOR select * from foo; fetch forward 1000 > from JDBC_CURS_588; > > with subsequent fetch forward queries being executed as the full result > set is pulled in. > > In the 8.0 driver I don't see this happening. I see only the "select * > from foo" query in the postgresql server log. > > Is the query result still being sent in batch chunks of 1000 rows, but > using a different mechanism? > > Thanks! > > -- Alan > > > > ---------------------------(end of broadcast)--------------------------- > TIP 6: Have you searched our list archives? > > http://archives.postgresql.org -- Dave Smith CANdata Systems Ltd 416-493-9020
В списке pgsql-jdbc по дате отправления: