Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (herse.apache.org: local policy)
Date: Wed, 06 Dec 2006 18:50:20 +0100
From: =?ISO-8859-1?Q?=D8ystein_Gr=F8vlen?= <Oystein.Grovlen@Sun.COM>
Subject: Re: Derby Client Driver and LOBs
In-reply-to: <66c10f230612060738m2aece198r349793382253d718@mail.gmail.com>
Sender: Oystein.Grovlen@Sun.COM
To: derby-dev@db.apache.org
Message-id: <457702DC.6000807@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 8BIT
References: <66c10f230612060248k62de54afg977009cb7ed8cf9f@mail.gmail.com>
 <4576D39E.8050702@basil.ocn.ne.jp>
 <66c10f230612060738m2aece198r349793382253d718@mail.gmail.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)

Dominique Pfister wrote:
 > I looked at the relevant parts of the derby client driver (version
 > 10.1.3.1) and quickly coded a  solution for large objects exceeding
 > 1MB, using temporary files that are deleted as soon as the blob is no
 > longer referenced. If there is interest, I could further refine my
 > solution and submit a patch.

Such a solution has been considered, but I fear it is not a general
solution.  Generally, we cannot assume that we have permission to
create files on the client side.  Instead, we want to be able to
stream the blob from the server without materializing it on the
server.

--
�ystein