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 "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2011/02/17 22:36:12 UTC
[jira] Updated: (DERBY-1134) Add a test to test that client
connection state is set properly and matches server behaviour for different
types of connections.
[ https://issues.apache.org/jira/browse/DERBY-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren updated DERBY-1134:
--------------------------------------
Urgency: Normal
Labels: derby_triage10_8 (was: )
> Add a test to test that client connection state is set properly and matches server behaviour for different types of connections.
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1134
> URL: https://issues.apache.org/jira/browse/DERBY-1134
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.2.1.6
> Reporter: Kathey Marsden
> Labels: derby_triage10_8
>
> We have seen many bugs where the client connection state is not correct and/or does not match the server. e.g DERBY-1044. It would be good to add a test to test that client connection state is set properly and matches server behaviour for different types of connections.
>
> State to check
> holdability
> autocommit
> transactionIsolation
> Types of Connections
> Connections obtained from Driver Manager
> Connections obtained from regular DataSource
> Connections obtained from PooledConnections
> - on initial connection.
> - after physical connection reset with getConnection()
> Connections obtained from XAConnections
> - PooledConnection tests above, but in addition check
> -in local transaction
> - after transitioning to a global transaction
> - after transitioning back to local transaction.
> For savepoints I added savepointJdbc30_XA.java that extends savepointJdbc30_JSR169 to add in testing for a different type of connection. I don't know if this is the right way to go to test different kinds of connections, for example a similar extension of setTransactionIsolation.java might be one way of testing isolation levels for the different types of connections.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira