| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Oliver Jowett <oliver(at)opencloud(dot)com> |
| Cc: | Sean Shanny <shannyconsulting(at)earthlink(dot)net>, David Wall <d(dot)wall(at)computer(dot)org>, pg(at)fastcrypt(dot)com, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: JDBC and processing large numbers of rows |
| Date: | 2004-05-12 03:28:36 |
| Message-ID: | 19456.1084332516@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Oliver Jowett <oliver(at)opencloud(dot)com> writes:
> 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.
FWIW, the backend's parser does go out of its way to discard empty
statements (a/k/a useless semicolons). I do not know how hard it would
be to teach JDBC's parser to do likewise, but it might be worth the
trouble if not too painful.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guido Fiala | 2004-05-12 06:37:42 | Re: JDBC and processing large numbers of rows |
| Previous Message | Tom Lane | 2004-05-12 03:23:30 | Re: Retrieve the postgres transaction id |