[ https://issues.apache.org/jira/browse/DERBY-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570971#action_12570971 ]
Mamta A. Satoor commented on DERBY-3404: ---------------------------------------- Knut, just wanted you to know that I have applied your patch to my codeline and running derbyall and junit tests because I have some changes of my own for DERBY-3404. If everything runs fine, then I will go ahead and commit your patch alongwith my changes tomorrow. > EmbedResultSet.getString() returns wrong value after auto-commit with > CLOSE_CURSORS_AT_COMMIT > --------------------------------------------------------------------------------------------- > > Key: DERBY-3404 > URL: https://issues.apache.org/jira/browse/DERBY-3404 > Project: Derby > Issue Type: Bug > Affects Versions: 10.3.1.4, 10.3.2.1, 10.4.0.0 > Reporter: Knut Anders Hatlen > Assignee: Knut Anders Hatlen > Priority: Minor > Attachments: CloseOnCommit.java, d3404-v1.diff, d3404-v1.stat > > > The following code prints "null" to the console with the embedded driver: > Statement s = c.createStatement(ResultSet.TYPE_FORWARD_ONLY, > ResultSet.CONCUR_READ_ONLY, > ResultSet.CLOSE_CURSORS_AT_COMMIT); > ResultSet rs = s.executeQuery("select * from sysibm.sysdummy1"); > rs.next(); > c.createStatement().executeQuery("values 1").close(); // causes > auto-commit > System.out.println(rs.getString(1)); > The call to rs.getString() should perhaps have thrown SQLException, since the > auto-commit between next() and getString() should close the ResultSet when > the holdability is CLOSE_CURSORS_AT_COMMIT, I think. Anyway, the value stored > in SYSIBM.SYSDUMMY1 is 'Y' and not NULL, so it should definitely not return > null. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.