[
https://issues.apache.org/jira/browse/DERBY-5341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-5341:
----------------------------------
Urgency: Urgent
Bug behavior facts: Deviation from standard,Embedded/Client
difference,Wrong query result (was: Embedded/Client difference,Wrong query
result)
Labels: derby_triage10_9 (was: )
Triage for 10.9. Marking Urgent since it has wrong results.
> Client allows insert of stream in excess of column with non-white space
> characters
> -----------------------------------------------------------------------------------
>
> Key: DERBY-5341
> URL: https://issues.apache.org/jira/browse/DERBY-5341
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Labels: derby_triage10_9
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
