Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: pass (athena.apache.org: domain of brett.wooldridge@gmail.com
 designates 74.125.82.50 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=references:from:in-reply-to:mime-version:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=rvAuAJQVuzKULExfgA3mkVEVfuDNsGKTY/JKfPzde6MpZTzA0AteIrTXCFIpJ8tSWb
         Y60BGM1gFO0D/9gAbfFwJLFWelYGZQ11gt6r+iEupRyX/FpHKK/dHsq8cMsIhXahs3eR
         r8Y9FkzLstFTPieNqyKWJ208cl7hRlZl+mzqM=
References: <AANLkTinVyZYXzGd63KOn61CTLnb-quxdzdCAtYHz6Zq2@mail.gmail.com>
 <wjo8oc69v670.fsf@oracle.com>
From: Brett Wooldridge <brett.wooldridge@gmail.com>
In-Reply-To: <wjo8oc69v670.fsf@oracle.com>
Mime-Version: 1.0 (iPhone Mail 8C148)
Date: Fri, 18 Feb 2011 22:59:37 +0900
Message-ID: <-3025694359845061665@unknownmsgid>
Subject: Re: BLOB streaming
To: Derby Discussion <derby-user@db.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

The question is, is it still fully materialized on the server before
streaming to the client?

Brett

Sent from my iPhone

On Feb 18, 2011, at 22:11, Knut Anders Hatlen <knut.hatlen@oracle.com> wrot=
e:

> Brett Wooldridge <brett.wooldridge@gmail.com> writes:
>
>> Hi all,
>>
>>
>> I just came across this in the manual, and if accurate raises some
>> concerns for me:
>>
>> For applications using the client driver, if the stream is stored in a
>> column of a type other than LONG VARCHAR or LONG VARCHAR FOR BIT DATA,
>> the entire stream must be able to fit into memory at one time. Streams
>> stored in LONG VARCHAR and LONG VARCHAR FOR BIT DATA columns do not
>> have this limitation.
>>
>> This seems to imply that if I have a BLOB containing 1GB of data, and
>> I'm using the client driver, the result cannot be streamed?
>> Can this possibly be correct? =EF=BF=BDGiven the apparent limit of VARCH=
AR of
>> ~32K, is there no way to stream large data to a client?
>
> A lot of work went into Derby 10.2 and Derby 10.3 to avoid the need to
> materialize LOBs on the client, so I believe this statement isn't true
> anymore. I've filed https://issues.apache.org/jira/browse/DERBY-5056 to
> update the manual.
>
> Thanks,
>
> --
> Knut Anders