[ http://issues.apache.org/jira/browse/DERBY-796?page=comments#action_12362863 ]
Daniel John Debrunner commented on DERBY-796: --------------------------------------------- After looking a little more, currently setBinaryStreamInternal is not suitable, though it should be! Also looking at this I think I saw a bug in the exsiting setClob(int, Clob) method. There a long is converted to an int, and it is assumed that if the long is out of range that the result will be a negative integer. That is not true. It would probably be worth changing setCharacterStreamInternal and setBinaryStreamInternal to take a long for the length, and perform the > max int check in the internal methods. setBinaryStreamInternal could be shared if a valid length is passed in always, which would mean changing setBlob(int, Blob) to pass the length to setBinaryStreamInternal, as is done in setClob. > jdbc 4.0 specific Blob and Clob method support > ---------------------------------------------- > > Key: DERBY-796 > URL: http://issues.apache.org/jira/browse/DERBY-796 > Project: Derby > Type: New Feature > Components: JDBC > Versions: 10.2.0.0 > Environment: jdbc 4.0 on all platforms > Reporter: V.Narayanan > Assignee: V.Narayanan > Priority: Minor > Fix For: 10.2.0.0 > Attachments: lob.diff > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
