[DERBY-5341] Client allows insert of stream in excess of column with non-white space characters

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 10.9.1.0
• Component/s: Network Client
• Labels: derby_triage10_11
• Urgency: Urgent
• Issue & fix info: High Value Fix, Repro attached
• Bug behavior facts: Deviation from standard, Embedded/Client difference, Wrong query result
• Assignee: Unassigned
• Reporter: Katherine Marsden
• Created: 15/Jul/11 20:29
• Updated: 03/Jul/13 15:26

Description

In converting LobLimits.java DERBY-1903 and trying to enable LobLimitsLiteTest with client. I discovered that this case fails with client:
try

{ insertClob2("ClobTest #9.1 ", conn, insertClob2, MORE_DATA_THAN_COL_WIDTH, 4, 1, MORE_DATA_THAN_COL_WIDTH, CHARDATAFILE); fail("ClobTest #9.1 " + "should have thrown XSDA4"); }

catch (SQLException sqle)

{ assertSQLState("XSDA4", sqle); }

// no row must be retrieved.
selectClob2("ClobTest #9.2 ", conn, selectClob2, BIG_LOB_SZ, 4, 0,
CHARDATAFILE);

If I omit the fail assertion, the row actually does get inserted and has presumably been truncated.
I will check in LobLimits.java soon with this bug number in the comments.
To reproduce, remove the if(!usingDerbyNetClient) condition and run the test largedata.LobLimitsLiteTest to reproduce the problem.

Issue Links

• is related to: DERBY-1903 Convert largedata/LobLimits.java to junit
• is related to: DERBY-5308 Investigate if largeData/LobLimits.java can be run for client