[DERBY-3898] Blob.setBytes differs between embedded and client driver when the specified length is invalid

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.3.3.0, 10.4.2.0, 10.5.1.1, 10.6.1.0
• Fix Version/s: 10.7.1.1
• Component/s: JDBC
• Labels: BLOB
• Urgency: Normal
• Issue & fix info: Newcomer
• Bug behavior facts: Embedded/Client difference
• Assignee: Yun Lee
• Reporter: Kristian Waagan
• Created: 02/Oct/08 16:32
• Updated: 29/Nov/10 14:21
• Resolved: 11/Aug/10 17:04

Description

Blob.setBytes behaves differently with the embedded driver and the client driver.
Assume a 1 byte array and a specified length of 2: Blob.setBytes(1, new byte[]

{0x69}

, 0, 2)
Embedded: IndexOutOfBoundsException (from java.io.RandomAccessFile.writeBytes or System.arraycopy)
Client: succeeds, returns insertion count 1

The behavior should be made consistent, but what is the correct behavior?

From the Blob.setBytes JavaDoc:
"Writes all or part of the given byte array to the BLOB value that this Blob object represents and returns the number of bytes written. Writing starts at position pos in the BLOB value; len bytes from the given byte array are written. The array of bytes will overwrite the existing bytes in the Blob object starting at the position pos. If the end of the Blob value is reached while writing the array of bytes, then the length of the Blob value will be increased to accomodate the extra bytes."

Issue Links

• is part of: DERBY-310 Document and/or change Derby client code to match behavior with Embedded driver where possible.
• is part of: DERBY-4609 Derby Test and Fix GSOC 2010 project