Blob setBytes and setBinaryStream Clarification Needed

Question

I'm writing a JDBC driver for SQL Server and working on the Blob implementation details.
One thing that is not clear in the JDBC spec to me at least is the behavior of the call to setBytes and to setBinaryStream on a Blob.
Say for a simple example I have a Blob with 5 bytes in it ->
1 2 3 4 5
AA BB CC DD EE
So in the database these 5 bytes are stored. I open a Blob on this field.
Then I call setBytes with offset of 3 and write bytes 11 22 33 44
Do I get this ->
1 2 3 4 5 6
AA BB 11 22 33 44 <- Writes over data, also past end of Blob.
Or this?
1 2 3 4 5
AA BB 11 22 33 <- Writes over data, but not past end of Blob.
Or this?
1 2 3 4 5 6 7 8 9
AA BB 11 22 33 44 CC DD EE <- Inserts data at offset, pushes existing data to right.
So in other words, does setBytes insert data at the insertion point, or start overwriting data at the insertion point? Also, does it allow you to keep writing the data in the backend Blob past the end of the Blob?
Same goes for setBinaryStream. The API spec is not clear about the desired behavior.
Thanks for any clues!
Matt

Answer 1

Well... looking at the API...
public void setBytes(int parameterIndex, byte[] x)
    throws SQLExceptionSets the designated parameter to the given Java array of bytes.
The driver converts this to an SQL VARBINARY or LONGVARBINARY
(depending on the argument's size relative to the driver's limits
on VARBINARY values) when it sends it to the database.
public void setBinaryStream(int parameterIndex, InputStream x,int length)
    throws SQLExceptionSets the designated parameter to the given input stream, which will
have the specified number of bytes. When a very large binary value
is input to a LONGVARBINARY parameter, it may be more practical to send
it via a java.io.InputStream object. The data will be read from the
stream as needed until end-of-file is reached.
It appears that setBytes() you pass in an entire in-memory array
of bytes, whereas setBinaryStream() allows you to pass in an
InputStream that contains the bytes.