db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4607) HeapScan test commits wrong connection
Date Tue, 06 Apr 2010 09:59:33 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12853831#action_12853831

Knut Anders Hatlen commented on DERBY-4607:

I plan to post a fix for this issue, but I'll wait until the fix for DERBY-4608 has been committed
in order to prevent conflicts (that fix also touches the HeapScan test).

> HeapScan test commits wrong connection
> --------------------------------------
>                 Key: DERBY-4607
>                 URL: https://issues.apache.org/jira/browse/DERBY-4607
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions:
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Minor
> The SELECT query in HeapScan is initialized like this:
>         select = openDefaultConnection().prepareStatement("SELECT * FROM "+tableName);
> The test cases commit the transaction like this:
>         getConnection().commit();
> openDefaultConnection() opens and returns a new connection to the default database, whereas
getConnection() returns a cached default connection, so the two connections are not the same,
and the transaction that's being committed is not the executing transaction.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message