Bryan Pendleton wrote:
> 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.
Hi Kristian and Bryan,
I am assuming that there is no out-of-memory specific exception implemented in Derby, and
that you by "out-of-memory exception" mean java.lang.OutOfMemoryError. Please
give me a hint if my assumption is wrong...
I believe it is important to distinguish between java Errors and Exceptions, since an
Error "indicates serious problems that a reasonable application should not try to
catch" [1].
--
John
[1] http://java.sun.com/j2se/1.5.0/docs/api/java/lang/Error.html
