db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sunitha Kambhampati <ksunitha...@gmail.com>
Subject Re: [jira] Commented: (DERBY-796) jdbc 4.0 specific Blob and Clob method support
Date Tue, 17 Jan 2006 15:51:43 GMT
V Narayanan - Sun Microsystems - Bangalore India wrote:

>Will the setBinaryStreamInternal method be raising an exception if the
>length variable doesn't fit inside an integer. Or is
>SetBinaryStreamInternal and the related classes being
>modified to work with the length variable as a long type.
An exception will be thrown in the setBinaryStreamInternal if the length 
variable doesnt fit inside an integer.

Currently there are lots of places in the language layer that expects 
the max size to be an int. e.g  DataTypeDescriptor.getMaximumWidth() 
api  returns an int.  I _do not plan _to change the int to long here, as 
it is outside the scope of DERBY-599 that I am currently working on.


>Sunitha Kambhampati (JIRA) wrote:
>>    [ http://issues.apache.org/jira/browse/DERBY-796?page=comments#action_12362867
>>Sunitha Kambhampati commented on DERBY-796:
>>I actually have a patch to fix Derby-599, where I am changing the setBlob(int,Blob)
to pass the length as is done in setClob to avoid materialization. I have some testing to
do before I post the patch to the list (hopefully will get it out in a day or two). I can
take care of changing the setBinaryStreamInternal to take a long for the length as part of
the Derby 599 patch as it is related. 

View raw message