Update of /cvsroot/springnet/Spring.Net/doc/reference/src
In directory sc8-pr-cvs8.sourceforge.net:/tmp/cvs-serv23617/src
Modified Files:
transaction.xml
Log Message:
SPRNET-776 - Unit tests for AdoPlatformTransactionManager
update docs to reflect limitations of AdoPlatformTransactionManager for nested transactions.
code cleanup in AdoTemplate, ConnectionUtils
Index: transaction.xml
===================================================================
RCS file: /cvsroot/springnet/Spring.Net/doc/reference/src/transaction.xml,v
retrieving revision 1.21
retrieving revision 1.22
diff -C2 -d -r1.21 -r1.22
*** transaction.xml 27 Nov 2007 21:01:42 -0000 1.21
--- transaction.xml 28 Nov 2007 05:54:37 -0000 1.22
***************
*** 1370,1376 ****
</table>
! <para>Please not that changing of isolation levels on a per-method basis
! is scheduled for RC1. Please check the forums for news on when this
! feature will be introduced into the nightly builds.</para>
<para>If you specify an exception type for 'NoRollbackFor' the action
--- 1370,1383 ----
</table>
! <para>Note that setting the TransactionPropagation to Nested will throw
! a NestedTransactionNotSupportedException in a case when actual nested
! transations occurs, i.e. not in the case of applying the Nested
! propagation but in fact no nested calls are made. This will be fixed for
! the Spring 1.2 release for SqlServer and Oracle which support nested
! transactions. Also note, that changing of isolation levels on a
! per-method basis is also scheduled for the Spring 1.2 release since it
! requires detailed command text metadata for each dbprovider.. Please
! check the forums for news on when this feature will be introduced into
! the nightly builds.</para>
<para>If you specify an exception type for 'NoRollbackFor' the action
***************
*** 1379,1382 ****
--- 1386,1398 ----
out to the calling code.</para>
+ <para>The ReadOnly boolean is a hint to the data access technology to
+ enable read-only optimizatations. This currenlty has no effect in
+ Spring's ADO.NET framework. If you would like to enable read-only
+ optimizations in ADO.NET this is generally done via the 'Mode=Read' or
+ 'Mode=Read-Only" options in the connection string. Check your database
+ provider for more information. In the case of NHibernate the flush mode
+ is set to Never when a new Session is created for the
+ transaction.</para>
+
<para>Throwing exceptions to indicate failure and assuming success is an
easier and less invasive programming model than performing the same task
|
