Changes between Version 17 and Version 18 of MapGuideRfc86

Timestamp:

09/24/09 20:12:40 (15 years ago)

Author:

leaf

Comment:

--

MapGuideRfc86

@@ -62 +62 @@
 }}}
 
-In the example above, it is possible that FDO connections used by executing SQL statements "SAVEPOINT X", "ROLLBACK TO X" and "COMMIT" are completely different FDO connections. If so, it will result in an error when executing SQL statement "ROLLBACK TO X" or "COMMIT".
-Sometimes, it can be resolved by passing an !MgTransaction instance when executing SQL statements because MapGuide Server will guarantee that operations in the same transaction use the same FDO connection. However, it still has the following two issues. 
+In the example above, it is possible that FDO connections used by executing SQL statements "SAVEPOINT X", "SAVEPOINT Y", "ROLLBACK TO X", "ROLLBACK TO Y" and "COMMIT" are completely different FDO connections. If so, it will result in an error when executing SQL statement "ROLLBACK TO X", "ROLLBACK TO Y" or "COMMIT". If it isn't a nested transaction, it can be resolved by passing an !MgTransaction instance when executing SQL statements because MapGuide Server will guarantee that operations in the same transaction use the same FDO connection. However, it still has the following two issues. 
   * There are only three methods supporting transaction, MgFeatureSerive::!UpdateFeatures, MgFeatureSerive::!ExecuteSqlQuery and MgFeatureSerive::!ExecuteSqlNoQuery.
   * MgFeatureSerive::!BeginTransaction will do something on the DRBMS serverwhen opening a transaction. This has consequences such as updates are only visible in this transaction, and data gets locked.