Changes between Version 2 and Version 3 of FDORfc16

Timestamp:

03/18/08 09:53:08 (17 years ago)

Author:

traianstanev

Comment:

--

FDORfc16

@@ -30 +30 @@
 == Proposed Solution ==
 
+The proposed SQLite provider will have the following features:
+
+* Data stored and consumed in native SQLite format, and therefore accessible to other SQLite-based applications;
+* Geometry will be serialized as BLOBs in FDO geometry format (FGF). Other ways that may be considered are storing points as X,Y columns and also geometry as WKB format;
+* A non-persistent, spatial index usable for BBOX queries built on the fly and valid for the duration of the FDO connection;
+* Execution of arbitrary SQL commands;
+* A metadata table where the geometry coordinate system is stored in WKT or EPSG form. In addition, PRJ files will be supported as alternative means of specifying a coordinate system when a metadata table is undesirable;
+* A tentative list of supported FDO commands : DescribeSchema, Select, SelectAggregates, Insert, Update, Delete, GetSpatialContexts, arbitrary SQL, ApplySchema, CreateDataStore;
+
+FDO features the provider will likely *not* support:
+
+* Feature class inheritance;
+* Geometry filters other than BBOX;
+* FDO Transactions -- but you can still manually execute BEGIN/COMMIT around other FDO commands;
+* Any other exotic feature you can think of.
 
 
@@ -38 +53 @@
 == Test Plan ==
 
-How the proposed change will be tested, if applicable.  New unit tests should be detailed here???
+There will be a small test suite that tests often used functionality. Arbitrary SQL execution will not be tested extensively.
 
 == Funding/Resources ==