Changes between Version 12 and Version 13 of MapGuideRfc86


Ignore:
Timestamp:
09/24/09 19:50:11 (15 years ago)
Author:
leaf
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • MapGuideRfc86

    v12 v13  
    3131In 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".
    3232Sometimes, 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.
    33   * There are only three methods supporting transaction, MgFeatureSerive::!UpdateFeatures, MgFeatureSerive::!ExecuteSqlQuery and MgFeatureSerive::ExecuteSqlNoQuery.
    34  * 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.
     33  * There are only three methods supporting transaction, MgFeatureSerive::!UpdateFeatures, MgFeatureSerive::!ExecuteSqlQuery and MgFeatureSerive::!ExecuteSqlNoQuery.
     34  * 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.
    3535
    3636{{{