[ http://issues.apache.org/jira/browse/DERBY-1323?page=all ]
Dag H. Wanvik updated DERBY-1323: --------------------------------- Attachment: DERBY-1323-2.stat DERBY-1323-2.diff This is version 2 of this patch. It addresses both comments of Fernanda's review. Changes were only made to client code and SURTest.java, so i ran derbynetclientmats again as well as SURTest on embedded without problems(*). (*) derbynetclientmats failed on NSinSameJVM.java and DerbyNetNewServer, though - I don't think it is related; I ran on a sane build from the classes directory with Sun JDK 1.5. > Detectability methods rowUpdated, rowInserted, rowDeleted can be called from > illegal states in both clients > ----------------------------------------------------------------------------------------------------------- > > Key: DERBY-1323 > URL: http://issues.apache.org/jira/browse/DERBY-1323 > Project: Derby > Type: Bug > Components: JDBC, Network Client > Versions: 10.2.0.0 > Reporter: Dag H. Wanvik > Priority: Minor > Fix For: 10.2.0.0 > Attachments: DERBY-1323-1.diff, DERBY-1323-1.stat, DERBY-1323-2.diff, > DERBY-1323-2.stat, Main.java > > Please see enclosed repro. > These detectability methods fail to check that they can be called in > some states. In the repro, calls are allowed while on insert row and > when after last row. These should both fail. Both clients have the > same problem. All three detectability methods have the same problem. > (repro only shows it for a subset of the cases). -- 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