Changes between Version 20 and Version 21 of MapGuideRfc78

Timestamp:

07/15/09 02:53:31 (16 years ago)

Author:

klain

Comment:

--

MapGuideRfc78

@@ -75 +75 @@
 
 Changes to Feature Service
+
+ExecuteSqlQuery() and ExecuteSqlNonQuery() must use the same underlying connection on which the transaction started. So MgTransaction instance is passed in as parameters for both of these two methods. The MgTransaction implementation can return the undelying connection. 
+
 {{{
 /// \brief
@@ -110 +113 @@
 One example using the new API
 {{{
-MgTransaction tran = AcMapFeatureService::StartTransaction(resourceId);
+MgTransaction* tran = AcMapFeatureService::StartTransaction(resourceId);
 AcMapFeatureService::ExecuteSql(resourceId, sql statement1, tran); 
 AcMapFeatureService::ExecuteSql(resourceId, sql statement2, tran); 
@@ -120 +123 @@
 If an MgTransaction has been started but hasn't been committed or rollbacked within the timeout, the transaction will be automatically rollbacked. If you call Commit() or Rollback() after timeout, an exception will be thrown reminding that the transaction has been timeout. 
 
+Two items will be added into WebConfig.ini for transaction timeout setting. If the transaction hasn't been committed or rollbacked within thirty minutes, it will be automatically rollbacked. 
+
+DataTransactionTimeout             = 1800
+DataTransactionTimerInterval       = 300
+
 Bind MgTransaction to FDO connection
 
-The transaction has to be bound with the underlying FDO connection where it starts during its life circle. The underlying FDO connection will be kept used by the transaction until the call of either Commit() or Rollback(). 
+The transaction has to be bound with the underlying FDO connection where it starts during its life circle. The underlying FDO connection will be kept used by the transaction until the call of either Commit() or Rollback(). The implementation of MgTransaction should be able to return the underlying connection. 
 
 == Implications ==