[DERBY-3574] With client, attempting to get the lob length after commit or connection close if there was a call to length() before commit does not throw an exception

• Type: Bug
• Status: Closed
• Priority: Trivial
• Resolution: Fixed
• Affects Version/s: 10.3.3.0, 10.4.2.0, 10.5.1.1
• Fix Version/s: 10.4.2.0, 10.5.1.1
• Component/s: JDBC, Network Client
• Assignee: Tiago R. Espinha
• Reporter: Katherine Marsden
• Created: 27/Mar/08 17:57
• Updated: 17/Jul/09 16:48
• Resolved: 15/Apr/08 20:55

Description

Attempting to get call Blob/Clob.length() after commit or connection close does not fail if there was a previous call to length(). If no previous call was made an exception is thrown as expected.

See attached program TestLobLength for repro with commit. If you comment out the two lines to get the length before the commit we get the expected exception.

Issue Links

• is related to: DERBY-3469 Clob.length() doesn't detect a closed underlying connection in a consistent way
• relates to: DERBY-4224 Commit after setAsciiStream() makes execution fail with the client driver
• relates to: DERBY-4312 SQLException XJ215 on insert with setCharacterStream() and autocommit off in mailjdbc test