Changes between Version 3 and Version 4 of FDORfc16

Timestamp:

Mar 18, 2008, 9:54:06 AM (16 years ago)

Author:

traianstanev

Comment:

--

FDORfc16

@@ -32 +32 @@
 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;
+ * 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.
+ * 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.