Hello Kristian.
The OutOfMemoryError I have been talking about when reading LOBs with
unknown length on the client side, is an exception thrown by the JVM
when the LOB data cannot fit into the heap space. I did not plan to
throw this error myself.
Oh, I mistaken your thought.
I thought that you limit max length of LOB in the program and throw
exception intentionally.
Please forget my previous mistaken comment.
Best regards.
Kristian Waagan wrote:
TomohitoNakayama wrote:
Hello.
IMHO, I think java.lang.IndexOutOfBoundsException is better than
java.lang.OutOfMemoryError for this situation ...
Error is too much for ...
Hi Tomohito,
Not sure I understand what you are referring to in your comment. I'll
describe the situation I think you are talking about. Please correct
me if I'm mistaken.
The OutOfMemoryError I have been talking about when reading LOBs with
unknown length on the client side, is an exception thrown by the JVM
when the LOB data cannot fit into the heap space. I did not plan to
throw this error myself.
Further, if there is enough memory on the client to hold more than 2
GB of data, and the user passes in a stream with more than 2 GB of
data available, I thought a SQLException would be in place:
22004.S.4=The length ({0}) exceeds the maximum length for the data
type ({1}).
Not quite sure what to put into {{0}}, but maybe Integer._MAX_VALUE?
Are we on the same track here, or are you referring to another situation?
Regards,
--
/*
Tomohito Nakayama
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Naka
http://www5.ocn.ne.jp/~tomohito/TopPage.html
*/
