db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Satheesh Bandaram <sathe...@Sourcery.Org>
Subject Re: BLOB : java.lang.OutOfMemoryError
Date Wed, 31 Aug 2005 18:04:54 GMT
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<body bgcolor="#ffffff" text="#000000">
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.<br>
Daniel John Debrunner wrote:
<blockquote cite="mid4315E664.4080403@debrunners.com" type="cite">
  <pre wrap="">Michael J. Segel wrote:

  <blockquote type="cite">
    <pre wrap="">On Wednesday 31 August 2005 10:49, Satheesh Bandaram wrote:

    <blockquote type="cite">
      <pre wrap="">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

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


    <pre wrap="">[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 

I guess it goes more to the point of why not have more focus on a "universal" 
  <pre wrap=""><!---->
My view

<a class="moz-txt-link-freetext" href="http://mail-archives.apache.org/mod_mbox/db-derby-dev/200508.mbox/%3c430A43DE.3060803@debrunners.com%3e">http://mail-archives.apache.org/mod_mbox/db-derby-dev/200508.mbox/%3c430A43DE.3060803@debrunners.com%3e</a>

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



View raw message