Re: JDBC driver's (non-)handling of InputStream:s - Mailing list pgsql-jdbc

From Kris Jurka
Subject Re: JDBC driver's (non-)handling of InputStream:s
Date
Msg-id Pine.BSO.4.56.0403301710580.9847@leary.csoft.net
Whole thread Raw
In response to Re: JDBC driver's (non-)handling of InputStream:s  (Oliver Jowett <oliver@opencloud.com>)
Responses Re: JDBC driver's (non-)handling of InputStream:s  (Oliver Jowett <oliver@opencloud.com>)
List 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

pgsql-jdbc by date:

Previous
From: Alan Stange
Date:
Subject: Re: V3 protocol, batch statements and binary transfer
Next
From: Oliver Jowett
Date:
Subject: Re: JDBC driver's (non-)handling of InputStream:s