db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryan Pendleton <bpendle...@amberpoint.com>
Subject Re: [jira] Commented: (DERBY-1471) Implement layer B streaming for new methods defined in JDBC4.0
Date Tue, 04 Jul 2006 16:37:23 GMT
 > Kristian Waagan commented on DERBY-1471:
 > ----------------------------------------
 > The approach is to exhaust the application stream and copy it into
 > memory to determine the length. If the data is too big to fit in memory,
 > the client will fail with an out-of-memory exception.

That seems fine to me. This is already the case with the current
API and implementation, I believe, so we aren't making anything worse.

In practice, do application programs end up having *two* copies of the
BLOB/CLOB in client-side memory at the same time, one copy inside the Derby
code and one copy in the application code? Or is there actually only a
single copy of the BLOB/CLOB in memory? I'm asking only because it seems
like we might want to be clear about this in our documentation.



View raw message