Issue Details (XML | Word | Printable)

Key: NUCCORE-1129
Type: New Feature New Feature
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Andy Jefferson
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
DataNucleus Core

Add persistence property to allow single connection to be used for a PM/EM, shared between transactional and nontransactional operations

Created: 17/Feb/14 02:35 PM   Updated: 01/Mar/14 07:39 PM   Resolved: 17/Feb/14 02:51 PM
Component/s: Datastore Support, Transactions
Affects Version/s: None
Fix Version/s: 4.0.0.m1


 Description  « Hide
When the store plugin defines one ConnectionFactory for transactional operations and one ConnectionFactory for nontransactional operations (e.g RDBMS), it would be desirable to be able to have a single connection for a PM/EM, that is used by transactional and nontransactional ops, to save the reallocation. This could be enabled by a persistence property like

datanucleus.connection.singleConnectionPerExecutionContext

Andy Jefferson made changes - 17/Feb/14 02:51 PM
Field Original Value New Value
Description When the store plugin defines one ConnectionFactory for transactional operations and one ConnectionFactory for nontransactional operations (e.g RDBMS), it would be desirable to be able to just get connections from the primary ConnectionFactory for nontransactional ExecutionContext operations. We could allow a persistence property
datanucleus.connection.nontx.usePrimaryConnectionFactory
(defaulting to false).
When the store plugin defines one ConnectionFactory for transactional operations and one ConnectionFactory for nontransactional operations (e.g RDBMS), it would be desirable to be able to just get connections from the primary ConnectionFactory for nontransactional ExecutionContext operations. We could allow a persistence property
datanucleus.connection.nontx.usePrimaryFactory
(defaulting to false).
Andy Jefferson added a comment - 17/Feb/14 02:51 PM
GitHub master has this now

Andy Jefferson made changes - 17/Feb/14 02:51 PM
Status Open [ 1 ] Resolved [ 5 ]
Resolution Fixed [ 1 ]
Andy Jefferson made changes - 18/Feb/14 05:07 PM
Summary Add persistence property to allow use of primary ConnectionFactory when nontransactional Add persistence property to allow single connection to be used for a PM/EM, shared between transactional and nontransactional operations
Description When the store plugin defines one ConnectionFactory for transactional operations and one ConnectionFactory for nontransactional operations (e.g RDBMS), it would be desirable to be able to just get connections from the primary ConnectionFactory for nontransactional ExecutionContext operations. We could allow a persistence property
datanucleus.connection.nontx.usePrimaryFactory
(defaulting to false).
When the store plugin defines one ConnectionFactory for transactional operations and one ConnectionFactory for nontransactional operations (e.g RDBMS), it would be desirable to be able to have a single connection for a PM/EM, that is used by transactional and nontransactional ops, to save the reallocation. This could be enabled by a persistence property like

datanucleus.connection.singleConnectionPerExecutionContext
Andy Jefferson made changes - 01/Mar/14 07:39 PM
Status Resolved [ 5 ] Closed [ 6 ]