Changes between Version 39 and Version 40 of FDORfc33

Timestamp:

04/17/09 10:21:53 (16 years ago)

Author:

gregboone

Comment:

--

FDORfc33

@@ -23 +23 @@
 == Motivation ==
 
-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. 
+The FDO API currently defines support for a SQL command that allows for pass-through execution of SQL statements either through !NonQuery execution of the SQL statement directly in the underlying Data Store, or through a query mechanism that returns a simple data reader listing the properties returned as a result of the SQL execution. The definition of the SQL command has remained fairly static over the last number of releases as primary development efforts have focused on extending other aspects of the FDO API, implementing new providers, etc. However, over the last few releases, requirements for change to the SQL command have accumulated as RDBMS providers have implemented SQL support and clients have attempted to integrate use of the 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. 
+
+Other more SQL specific requirements have also arisen, including:
+
+    - A need to allow a client to set the size of the fetch array an FDO provider will use when executing the SQL statement
+    - A need to specify an array of data values on which the command will be executed
+    - A need to specify the type of SQL command being execution, being either straight text or a stored procedure
+    - A need to specify the direction in which parameters to the SQL command are to be used, specifically, Input, Output, Input/Output or Return parameters
+
+This RFC will outline changes that are required in the FDO API to accommodate these requests.
 
 == Overview ==