"The client driver fully materializes LOBS when the row is retrieved" which would of course explain those errors when the data gets too large. Is this limitation being addressed? Or is there some other way of retrieving binary data from a standalone derby database that bypasses it?
DERBY-208 is filed to address this. Fernanda has started a discussion on how to implement a locator-based implementation. Hopefully this can be implemented for the next release.
-- Øystein
