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)" <de...@db.apache.org> on 2006/03/29 21:46:38 UTC

[jira] Created: (DERBY-1165) A test checking the transaction ids returned by xa_recover is needed

A test checking the transaction ids returned by xa_recover is needed
--------------------------------------------------------------------

         Key: DERBY-1165
         URL: http://issues.apache.org/jira/browse/DERBY-1165
     Project: Derby
        Type: Test
    Reporter: Knut Anders Hatlen
    Priority: Minor


jdbcapi/xaSimplePositive.sql tests xa_recover, but the transaction ids are filtered out because of an ordering problem (see DERBY-977). A new test that checks that the correct transaction ids are returned should be written. For instance, xaSimplePositive.sql could be rewritten as a java/JUnit test.

-- 
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


[jira] Updated: (DERBY-1165) A test checking the transaction ids returned by xa_recover is needed

Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-1165?page=all ]

Knut Anders Hatlen updated DERBY-1165:
--------------------------------------

    Affects Version/s: 10.2.1.6

> A test checking the transaction ids returned by xa_recover is needed
> --------------------------------------------------------------------
>
>                 Key: DERBY-1165
>                 URL: http://issues.apache.org/jira/browse/DERBY-1165
>             Project: Derby
>          Issue Type: Test
>          Components: Test
>    Affects Versions: 10.2.1.6
>            Reporter: Knut Anders Hatlen
>            Priority: Minor
>
> jdbcapi/xaSimplePositive.sql tests xa_recover, but the transaction ids are filtered out because of an ordering problem (see DERBY-977). A new test that checks that the correct transaction ids are returned should be written. For instance, xaSimplePositive.sql could be rewritten as a java/JUnit test.

-- 
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

        

[jira] Closed: (DERBY-1165) A test checking the transaction ids returned by xa_recover is needed

Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-1165?page=all ]

Knut Anders Hatlen closed DERBY-1165.
-------------------------------------

    Resolution: Won't Fix

> A test checking the transaction ids returned by xa_recover is needed
> --------------------------------------------------------------------
>
>                 Key: DERBY-1165
>                 URL: http://issues.apache.org/jira/browse/DERBY-1165
>             Project: Derby
>          Issue Type: Test
>          Components: Test
>    Affects Versions: 10.2.1.6
>            Reporter: Knut Anders Hatlen
>            Priority: Minor
>
> jdbcapi/xaSimplePositive.sql tests xa_recover, but the transaction ids are filtered out because of an ordering problem (see DERBY-977). A new test that checks that the correct transaction ids are returned should be written. For instance, xaSimplePositive.sql could be rewritten as a java/JUnit test.

-- 
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

        

[jira] Commented: (DERBY-1165) A test checking the transaction ids returned by xa_recover is needed

Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/DERBY-1165?page=comments#action_12456740 ] 
            
Knut Anders Hatlen commented on DERBY-1165:
-------------------------------------------

Since this is already tested in jdk>1.3, and jdk 1.3 will not be supported in 10.3, I suggest that we close the issue as "Won't Fix".

> A test checking the transaction ids returned by xa_recover is needed
> --------------------------------------------------------------------
>
>                 Key: DERBY-1165
>                 URL: http://issues.apache.org/jira/browse/DERBY-1165
>             Project: Derby
>          Issue Type: Test
>          Components: Test
>    Affects Versions: 10.2.1.6
>            Reporter: Knut Anders Hatlen
>            Priority: Minor
>
> jdbcapi/xaSimplePositive.sql tests xa_recover, but the transaction ids are filtered out because of an ordering problem (see DERBY-977). A new test that checks that the correct transaction ids are returned should be written. For instance, xaSimplePositive.sql could be rewritten as a java/JUnit test.

-- 
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

        

[jira] Updated: (DERBY-1165) A test checking the transaction ids returned by xa_recover is needed

Posted by "Mike Matrigali (JIRA)" <de...@db.apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-1165?page=all ]

Mike Matrigali updated DERBY-1165:
----------------------------------

    Component: Test

> A test checking the transaction ids returned by xa_recover is needed
> --------------------------------------------------------------------
>
>          Key: DERBY-1165
>          URL: http://issues.apache.org/jira/browse/DERBY-1165
>      Project: Derby
>         Type: Test

>   Components: Test
>     Reporter: Knut Anders Hatlen
>     Priority: Minor

>
> jdbcapi/xaSimplePositive.sql tests xa_recover, but the transaction ids are filtered out because of an ordering problem (see DERBY-977). A new test that checks that the correct transaction ids are returned should be written. For instance, xaSimplePositive.sql could be rewritten as a java/JUnit test.

-- 
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


[jira] Commented: (DERBY-1165) A test checking the transaction ids returned by xa_recover is needed

Posted by "Myrna van Lunteren (JIRA)" <de...@db.apache.org>.
    [ http://issues.apache.org/jira/browse/DERBY-1165?page=comments#action_12372318 ] 

Myrna van Lunteren commented on DERBY-1165:
-------------------------------------------

Note, that the rewriting needs to focus on jdk1.3 - I think the test jdbcapi/XATest.java already includes the details of xaSimplePositive.sql but doesn't run with jdk1.3, which is why xaSimplePositive.sql was kept alive.



> A test checking the transaction ids returned by xa_recover is needed
> --------------------------------------------------------------------
>
>          Key: DERBY-1165
>          URL: http://issues.apache.org/jira/browse/DERBY-1165
>      Project: Derby
>         Type: Test
>     Reporter: Knut Anders Hatlen
>     Priority: Minor

>
> jdbcapi/xaSimplePositive.sql tests xa_recover, but the transaction ids are filtered out because of an ordering problem (see DERBY-977). A new test that checks that the correct transaction ids are returned should be written. For instance, xaSimplePositive.sql could be rewritten as a java/JUnit test.

-- 
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