Re: BLOB : java.lang.OutOfMemoryError

[Satheesh Bandaram]

Right... Network server currently sends whole datatype over to client. While this works for most datatypes, since they are limited in size, it may be a problem for clob/blob types. Server needs to be able to stream these large datatypes over the wire on demand, so no matter whether we have a common client or not, server needs to be enhanced. Satheesh Daniel John Debrunner wrote: Michael J. Segel wrote: On Wednesday 31 August 2005 10:49, Satheesh Bandaram wrote: Thanks for the offer.. It would really be great to have more developpers working on Derby. Join the derby-dev alias to participate in the development. Derby embedded driver already has the capability to stream blob/clob, without requiring reading them completely into memory. It would be great to enhance Derby network server and Derby client to support this kind of behavior. Satheesh [SNIP] This may be a dumb question... Maybe its hindsight, but why isn't the Server Framework either a subclass or an extension to the embedded driver? Someone had posted that the Network Driver utilized the embedded driver... (Or is that bathtub gin affecting my memory?) I guess it goes more to the point of why not have more focus on a "universal" driver? My view http://mail-archives.apache.org/mod_mbox/db-derby-dev/200508.mbox/[EMAIL PROTECTED] Really the two drivers are doing different things, one has to convert requests into messages using DRDA over tcp/ip, the other just calls java methods. Dan.