On Wed, 21 Apr 2004, Oliver Jowett wrote:
> This patch allows bytea parameters set via setBytes() /
> setBinaryStream() to be streamed to the backend. With the patch applied,
> the additional memory overhead for bytea parameters is small and
> independent of how large the parameter data is.
Have you given any consideration to extending this to handle streaming
large text fields via setAsciiStream(), setUnicodeStream(), or
setObject(int, Object, Types.LONGVARCHAR) ? Also updateable ResultSets
have similar updateXXX to PreparedStatement's setXXX methods that could
benefit from a streaming interface.
There is also the implied assumption that V3 protocol implies a unicode
client encoding which implies a seven bit safe streaming option which
would be better spelled out in a comment or called in a way that used the
encoding variable to derive this fact.
Kris Jurka
