[ http://issues.apache.org/jira/browse/DERBY-2017?page=comments#action_12456452 ] Bryan Pendleton commented on DERBY-2017: ----------------------------------------
Hi Saurabh, After the discussion on the mailing list regarding this issue I'm still confused. Does your change proposal make the network client configuration's behavior match the embedded system behavior? Or do the two configurations behave differently? See this part of the discussion: http://www.nabble.com/forum/ViewPost.jtp?post=7735323&framed=y I'm worried that it is incorrect to roll back the entire transaction for this error; that only the statement that caused the LOB problem should be rolled back. > Client driver can insert and commit partial data when a LOB stream throws > IOException or does not match the specified length > ---------------------------------------------------------------------------------------------------------------------------- > > Key: DERBY-2017 > URL: http://issues.apache.org/jira/browse/DERBY-2017 > Project: Derby > Issue Type: Bug > Components: JDBC, Network Client > Affects Versions: 10.2.1.6 > Reporter: Knut Anders Hatlen > Assigned To: Saurabh Vyas > Fix For: 10.3.0.0, 10.2.2.0 > > Attachments: Derby_2017_v1.diff, Derby_2017_v1.stat, > StreamErrRepro.java > > > When a LOB stream throws an exception or does not match the specified length, > the client driver does not raise an exception until it has finished executing > the statement. Therefore, the statement will be executed (and possibly > committed) on the server even though the client reports that the statement > failed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
