Changes between Version 38 and Version 39 of FDORfc33

Timestamp:

04/17/09 10:07:47 (16 years ago)

Author:

gregboone

Comment:

--

FDORfc33

@@ -23 +23 @@
 == Motivation ==
 
-Enable the FDO API to support SQL pass-through commands that return an FDO feature reader, referencing a proper FDO schema, not simply an FDO data reader. The feature reader will contain proper geometry properties, relations and associations. This enhancement is also intended to allow client applications that use FDO Feature Readers to code their applications in a generic manner so that data coming back from Select or SQL Pass Through statements can be processed in a uniform manner, thus reducing complexity, costs and time to implement. 
+The FDO API currently defines support for a SQL command that allows for pass-through execution of SQL statements as a !NonQuery or as a query that return a simple data reader listing the data (or column in the case of SQL) properties returned as a result of the execution. The definition of the SQL command has remained static over the last number of releases as primary development effort focused on extending other aspects of the FDO API, implementing new providers, etc. However, over the last few releases some requirements for change have accumulated as RDBMS providers have implemented SQL command support and clients have attempted to integrate use of the SQL command into their applications in a seamless manner. 
+
+One key request that has been received, has been the desire to have the FDO API support SQL pass-through commands that return an FDO feature reader, referencing a proper FDO schema, not simply an FDO data reader. The feature reader will contain proper geometry properties, relations and associations. This enhancement is also intended to allow client applications that use FDO Feature Readers to code their applications in a generic manner so that data coming back from Select or SQL Pass Through statements can be processed in a uniform manner, thus reducing complexity, costs and time to implement. 
 
 == Overview ==
@@ -175 +177 @@
 
     /// \brief
-    /// Gets the record set fetch size that is to be used by
-    /// the command when executing statements against the 
+    /// Gets the fetch size of the data set used by
+    /// the SQL command when executing statements against the 
     /// underlying Data Store. This parameter is typically set 
-    /// in situations where large amout of data is expected. 
-    /// providers will want to minimize the Data Store round 
-    /// trips: For example tetch 10,000 rows in one execution step. 
+    /// in situations where large amout of data are expected 
+    /// when the SQL command is executed and providers need 
+    /// to minimize the number of Data Store round trips
+    /// For example, fetch 10,000 rows in one execution step. 
     /// 
     /// \return
@@ -188 +191 @@
 
     /// \brief
-    /// Sets the record set fetch size that is to be used by
-    /// the command when executing statements against the 
+    /// Sets the fetch size of the data set used by
+    /// the SQL command when executing statements against the 
     /// underlying Data Store. This parameter is typically set 
-    /// in situations where large amout of data is expected. 
-    /// providers will want to minimize the Data Store round 
-    /// trips: For example tetch 10,000 rows in one execution step. 
+    /// in situations where large amout of data are expected 
+    /// when the SQL command is executed and providers need 
+    /// to minimize the number of Data Store round trips
+    /// For example, fetch 10,000 rows in one execution step. 
     /// 
     /// \param value