| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Oliver Jowett <oliver(at)opencloud(dot)com> |
| Cc: | Peter Schuller <peter(dot)schuller(at)infidyne(dot)com>, PostgreSQL JDBC Mailing List <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: JDBC driver's (non-)handling of InputStream:s |
| Date: | 2004-03-30 22:15:20 |
| Message-ID: | Pine.BSO.4.56.0403301710580.9847@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Tue, 30 Mar 2004, Oliver Jowett wrote:
> The "right way" to do it is to expand the driver's use of the V3
> protocol to use the extended query protocol; then the stream can be
> directly streamed to the backend without further
> translation/escaping/etc using a binary Bind parameter. But there's some
> infrastructure work to do before that can happen.
>
Can we really stream an InputStream directly to the backend? Don't we
need to prefix the message with a length argument? and the only way to
get this with the InputStream API is to read the whole thing. Yes, we can
avoid the translation/escaping, but I don't think we can avoid persisting
the InputStream at some point.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Jowett | 2004-03-30 22:39:58 | Re: JDBC driver's (non-)handling of InputStream:s |
| Previous Message | Alan Stange | 2004-03-30 22:10:32 | Re: V3 protocol, batch statements and binary transfer |