[
https://issues.apache.org/jira/browse/OPENJPA-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick reassigned OPENJPA-669:
------------------------------------
Assignee: Michael Dick
> NativeSequences can be incremented within the business transaction
> ------------------------------------------------------------------
>
> Key: OPENJPA-669
> URL: https://issues.apache.org/jira/browse/OPENJPA-669
> Project: OpenJPA
> Issue Type: Bug
> Affects Versions: 0.9.6, 0.9.7, 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.1.0
> Reporter: Michael Dick
> Assignee: Michael Dick
> Fix For: 1.2.0
>
>
> SQL Sequences are independent of the transaction. Therefore the same
> connection which is used to insert a row can be used to increment the
> sequence value.
> Currently we treat these native sequences in the same manner as updating a
> sequence table - ie the work will be done on connection2 (aka the
> non-jta-data-source). This appears to be unnecessary and requires an
> additional datasource when running in a managed environment which can't
> suspend the current transaction
> To resolve the problem I added a nativeSequenceType attribute to the
> DBDictionary class. This setting will be used to determine the whether the
> databases sequences are transactional, contiguous or non transactional
> (Default is contiguous). If the native sequences are transactional or
> contiguous they will be executed within the current transaction and will not
> require a second connection factory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
