Kathey Marsden wrote:
TomohitoNakayama wrote:
I think it is needed to find where excessive expanding code exists ....
I agree and think a good step toward that is to make sure there are
separate cases filed with reproducible cases for the issues that show
different symptoms. I am getting a little confused. What different
usage scenarios are at issue here?
Kathey
Two scenarios:
1. Insert a BLOB using prepared statement. The network server will
expand the entire BLOB into memory when streaming it from the client,
and if the BLOB is big, you will get OutOfMemoryError
2. Select a BLOB using a result set. The network client will expand the
entire BLOB into memory when streaming it from the server. If the BLOB
is big, you will get OutOfMemoryError.
Both of these scenarios are related to the fact the the receiving end of
a stream, will expand all data of the stream into memory. I think, if
this cannot be fixed, at least it should be documented (maybe it already
is).
--Andreas
- Re: [jira] Commented: (DERBY-550) BLOB : java.... Andreas Korneliussen
-
