[
https://issues.apache.org/jira/browse/DERBY-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamta A. Satoor updated DERBY-2490:
-----------------------------------
Urgency: Normal
Labels: derby_triage10_10 (was: )
> Clarify transaction management in LanguageConnectionContext.
> ------------------------------------------------------------
>
> Key: DERBY-2490
> URL: https://issues.apache.org/jira/browse/DERBY-2490
> Project: Derby
> Issue Type: Sub-task
> Components: SQL
> Reporter: Daniel John Debrunner
> Labels: derby_triage10_10
>
> LanguageConnectionContext has these four methods (as well as other
> commit/rollback methods) to manage transactions and specifically nested
> transactions.
> void beginNestedTransaction(boolean readOnly) throws StandardException;
> void commitNestedTransaction() throws StandardException;
> TransactionController getTransactionCompile();
> TransactionController getTransactionExecute();
> getTransactionCompile() returns the same as getTransactionExecute() if not in
> a nested transaction.
> nested transactions started out as "compile time" transactions but are now
> used at runtime, for example in permission lookup and identity columns(?),
> thus the name getTransactionCompile() can confuse readers.
> A cleaner api might be to just have a single getTransaction() method that
> returns the current transaction, which is main transaction (non-nested) except
> between calls to
> beginNestedTransaction()
> commitNestedTransaction()
> I think that is the logic today, one one transaction is active, either the
> nested one of the main one.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
