The reference manual says the following about memory requirements when streaming columns from the network client - http://db.apache.org/derby/docs/10.7/ref/rrefjavsqlprst.html:
> 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.
I believe this is not true any more. There was a lot of work to reduce the memory requirements for LOBs in Derby 10.2 and Derby 10.3, and I think the specific problem referred to in this section of the manual was fixed in