Skip site navigation (1) Skip section navigation (2)

Re: JDBC and processing large numbers of rows

From: Sean Shanny <shannyconsulting(at)earthlink(dot)net>
To: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: JDBC and processing large numbers of rows
Date: 2004-05-12 01:29:06
Message-ID: 40A17DE2.4030902@earthlink.net (view raw or flat)
Thread:
Lists: pgsql-jdbc
Oliver,

Thank you very much for clearing that up for me.  Learn something 
everyday on the postgres lists...

--sean

Oliver Jowett wrote:

> Sean Shanny wrote:
>
>> Make sure you do not end your SQL with a ; (semi colon) as that will 
>> cause the fetching part not to work.  Don't know why but it does. :-)
>
>
> Technically, "SELECT foo;" is two statements, "SELECT foo" and "", as 
> JDBC doesn't require a statement terminator. The (simple-minded) JDBC 
> query parser doesn't do anything special to ignore trailing empty 
> statements. And you can't DECLARE a cursor that runs two statements.. 
> so the driver says "two statements, can't use a cursor!".
>
> -O
>

In response to

pgsql-jdbc by date

Next:From: Dave CramerDate: 2004-05-12 02:33:30
Subject: Re: Retrieve the postgres transaction id
Previous:From: Oliver JowettDate: 2004-05-12 01:15:18
Subject: Re: JDBC and processing large numbers of rows

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group