db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kathey Marsden <kmarsdende...@sbcglobal.net>
Subject Re: [jira] Commented: (DERBY-3085) Fails to handle BLOB fields with a PreparedStatement with size >32750 bytes
Date Wed, 26 Sep 2007 22:53:05 GMT
Bryan Pendleton wrote:
> I vaguely recall discussions of
> such an algorithm during the LOB locator development, so there may
> in fact be such code in the client, but it's not working for some
> reason or another.

Thank you Bryan for looking at this.  Is the LOB locator development 
relevant to parameters being sent from the client or only LOBs being 
returned from the server?

> As I type this in, I realize that I'm fuzzy on whether this
> drain processing would be trigger by the server or by the client.
> Does the server have enough context to know when the client is
> done with one statement and moving on to the next?
It needs to be triggered by the server I think. After execution, any 
streams set in the parameters need to be drained, but as I think about 
this more I don't really understand how things would work with multiple 
parameters if  the parameter is only partially read from the network 
server stream.  It does seem to work ok as long as the streams are 
consumed by the server.  (See attached TestBlobMultipleParam.java).


View raw message