Changes between Version 11 and Version 12 of MapGuideRfc78

Timestamp:

07/09/09 23:18:56 (15 years ago)

Author:

klain

Comment:

--

MapGuideRfc78

@@ -30 +30 @@
 Currently MapGuide Feature Service supports executing a sequence of standard commands within a single transaction through the API illustrated below. The standard commands are delete/update/insert. If you pass in true for useTransaction, the API will start a transaction and commit(or rollback) it at the end. Thus all command execution will reside inside a single transaction. 
 {{{
-    virtual MgPropertyCollection* UpdateFeatures( MgResourceIdentifier* resource,
-                                                  MgFeatureCommandCollection* commands,
-                                                  bool useTransaction ) = 0;
+virtual MgPropertyCollection* UpdateFeatures( MgResourceIdentifier* resource,
+                                              MgFeatureCommandCollection* commands,
+                                              bool useTransaction ) = 0;
 }}}
 However, MapGuide Feature Service also provides another two APIs to execute sql statements as illustrated below, where a database transaction will internally be started and committed befor and after the sql statement execution. Here the capability of executing a sequence of sql statements within a single transaction is missing. 
 {{{
-    virtual INT32 ExecuteSqlNonQuery( MgResourceIdentifier* resource,
-                                      CREFSTRING sqlNonSelectStatement ) = 0;
-    virtual MgSpatialContextReader* GetSpatialContexts( MgResourceIdentifier* resource,
-                                                        bool bActiveOnly) = 0;
+virtual INT32 ExecuteSqlNonQuery( MgResourceIdentifier* resource,
+                                  CREFSTRING sqlNonSelectStatement ) = 0;
+virtual MgSpatialContextReader* GetSpatialContexts( MgResourceIdentifier* resource,
+                                                    bool bActiveOnly) = 0;
 }}}
 This proposal is to extend Feature Service to support executing a sequence of sql statements within a single transaction. 
@@ -46 +46 @@
 
 A new class of MgTransaction will be added to represent a transaction to be performed in a data store. 
+{{{
+/// \brief
+/// MgTransaction represents a transaction to be performed in a DataStore.
+/// If the transaction is time out, commit or rollback a transaction will
+/// result in one exception MgFeatureServiceException thrown.
+class MgTransaction : public MgGuardDisposable
+{
+PUBLISHED_API:
+    /// \brief
+    /// Commit the transaction.
+    ///
+    virtual void Commit() = 0;
 
+    /// \brief
+    /// Rollback the transaction.
+    ///
+    virtual void Rollback() = 0;
+
+    /// \brief
+    /// Get the identifier of feature source associated with the transaction.
+    ///
+    /// \return
+    /// Returns the identifier of feature source associated with the transaction.
+    ///
+    virtual MgResourceIdentifier* GetFeatureSource() = 0;
+};
+}}}
 == Implications ==