You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-commits@db.apache.org by dj...@apache.org on 2007/03/28 22:12:06 UTC
svn commit: r523450 -
/db/derby/code/trunk/java/engine/org/apache/derby/iapi/store/access/TransactionController.java
Author: djd
Date: Wed Mar 28 13:12:05 2007
New Revision: 523450
URL: http://svn.apache.org/viewvc?view=rev&rev=523450
Log:
Clarify nested connection behaviour in TransactionController following some discussion in DERBY-2490.
Modified:
db/derby/code/trunk/java/engine/org/apache/derby/iapi/store/access/TransactionController.java
Modified: db/derby/code/trunk/java/engine/org/apache/derby/iapi/store/access/TransactionController.java
URL: http://svn.apache.org/viewvc/db/derby/code/trunk/java/engine/org/apache/derby/iapi/store/access/TransactionController.java?view=diff&rev=523450&r1=523449&r2=523450
==============================================================================
--- db/derby/code/trunk/java/engine/org/apache/derby/iapi/store/access/TransactionController.java (original)
+++ db/derby/code/trunk/java/engine/org/apache/derby/iapi/store/access/TransactionController.java Wed Mar 28 13:12:05 2007
@@ -626,9 +626,11 @@
* startNestedUserTransaction() call, and let the child transaction be the
* transaction returned by the startNestedUserTransaction() call.
* <p>
- * Only 1 non-readOnly nested user transaction can exist. If a subsequent
- * non-readOnly transaction creation is attempted prior to destroying an
- * existing write nested user transaction an exception will be thrown.
+ * A parent transaction can nest a single readonly transaction
+ * and a single separate read/write transaction.
+ * If a subsequent nested transaction creation is attempted
+ * against the parent prior to destroying an existing
+ * nested user transaction of the same type, an exception will be thrown.
* <p>
* The nesting is limited to one level deep. An exception will be thrown
* if a subsequent getNestedUserTransaction() is called on the child