From: | Dmitry Tkach <dmitry(at)openratings(dot)com> |
---|---|
To: | Felipe Schnack <felipes(at)ritterdosreis(dot)br> |
Cc: | Rich Cullingford <rculling(at)sysd(dot)com>, pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: setFetchSize() |
Date: | 2003-07-17 17:16:15 |
Message-ID: | 3F16D9DF.6050900@openratings.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Felipe Schnack wrote:
> Seems to me like a quite good solution! But why this is needed when autocommit is off? I can't understand.
>
>
Because you can only have cursors declared inside a transaction :-(
Dima
>On Thu, 17 Jul 2003 13:01:43 -0400
>Dmitry Tkach <dmitry(at)openratings(dot)com> wrote:
>
>
>
>>Rich Cullingford wrote:
>>
>>
>>
>>>All,
>>>Will this function be implemented in Release 7.4? I have several arge
>>>tables that run Java out of memory when I attempt to load them through
>>>JDBC. Any workarounds arppreciated...
>>>
>>>
>>I was using cursors for a while as a workaround...
>>Something like this:
>>
>>c.setAutocommit (false);
>>Statement s = c.createStatement ();
>>s.execute ("declare foo cursor for select * from bar");
>>
>>while (true)
>>{
>> ResultSet rs = s.executeQuery ("fetch 10 from foo");
>> int count = 0;
>> while (rs.next ())
>> {
>> count++;
>> doStuffWithThisRow (rs);
>> }
>>
>> if (count < 10) //The whole cursor contents has been processed
>> break;
>>}
>>
>>
>>I hope, it helps...
>>
>>Dima
>>
>>
>>
>>---------------------------(end of broadcast)---------------------------
>>TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
>>
>>
>
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Felipe Schnack | 2003-07-17 17:19:03 | Re: setFetchSize() |
Previous Message | Patric Bechtel | 2003-07-17 17:11:44 | Re: setFetchSize() [Viruschecked] |