[
https://issues.apache.org/jira/browse/DERBY-5341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066280#comment-13066280
]
Kathey Marsden commented on DERBY-5341:
---------------------------------------
With revision 1147335 this can be reproduced by removing the
if(usingDerbyNetClient() block in LobLimitsTest and running
largedata.LobLimitsLiteTest:
// DERBY-5341 : Client allows clob larger than
// column width to be inserted.
if (!usingDerbyNetClient()) {
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);
}
}
> 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
> Reporter: Kathey Marsden
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
