Changes between Version 6 and Version 7 of MapGuideRfc78

Timestamp:

Jul 9, 2009, 10:26:56 PM (15 years ago)

Author:

klain

Comment:

--

MapGuideRfc78

@@ -24 +24 @@
 == Overview ==
 
-This section brefly describes the problem set, and the proposed solution in general terms.  It should be deliberately short, a couple of sentences or so.
+This proposal is to enhance the transaction capability of MapGuide Feature Service to support executing not only a sequence of standard commands(delete/update/insert) but also a sequence of sql statements within a single transaction. 
 
 == Motivation ==
 
-This is the most important part of the RFC.  It describes the problem domain in detail.  Focusing on this will allow reviewers to fully understand why the proposed change is being made, and potentially suggest different/better ways of accomplishing the desired results.  The more time we spend on understanding the problem, the better our solution will be.
+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;
+
+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;
+
+This proposal is to extend Feature Service to support executing a sequence of sql statements within a single transaction. 
 
 == Proposed Solution ==