[DERBY-5489] getBinary() returns incorrect data after getObject() call on BLOB column

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.7.1.1, 10.8.2.2
• Fix Version/s: 10.9.1.0
• Component/s: JDBC
• Labels: derby_backport_reject_10_8 derby_triage10_9
• Urgency: Normal
• Issue & fix info: Release Note Needed, Repro attached
• Bug behavior facts: Embedded/Client difference, Wrong query result
• Assignee: Kristian Waagan
• Reporter: Pawel Fronczak
• Created: 31/Oct/11 22:52
• Updated: 09/Feb/15 19:51
• Resolved: 26/Apr/12 07:27

Description

When ResultSet.getObject(int) is called on a BLOB column, the correct EmbedBlob object is returned. But if afterwards the ResultSet.getBytes(int) is called on the same row, the returned array contains invalid data - it is offset by 3 bytes and its size is incorrect.
The problem only occurs when the stored BLOB is large enough to be internally represented by stream and not by array of bytes (at least ~32KiB).
It seems that the getObject method shifts the stream position and therefore the getBytes method starts to read the data after the third byte, thus incorrectly calculating its length.

Issue Links

• is related to: DERBY-5696 Documentation on LOBs needs some fixes
• relates to: DERBY-6793 Stream or LOG value cannot be retrieved more than once