You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2008/02/12 15:03:10 UTC
[jira] Commented: (DERBY-3404) EmbedResultSet.getString() returns
wrong value after auto-commit with CLOSE_CURSORS_AT_COMMIT
[ https://issues.apache.org/jira/browse/DERBY-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568122#action_12568122 ]
Knut Anders Hatlen commented on DERBY-3404:
-------------------------------------------
The behaviour was changed by this commit:
------------------------------------------------------------------------
r537353 | kahatlen | 2007-05-12 10:11:08 +0200 (Sat, 12 May 2007) | 6 lines
DERBY-827 (partial) Performance can be improved by re-using language
ResultSets across Activation executions
Reset candidate row array between executions. Based on patch/ideas
from Dyre Tjeldvoll.
------------------------------------------------------------------------
> 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
> Priority: Minor
> Attachments: CloseOnCommit.java
>
>
> 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.