Changes between Version 7 and Version 8 of FDORfc43

Timestamp:

10/28/09 01:54:45 (15 years ago)

Author:

zspitzer

Comment:

--

FDORfc43

@@ -55 +55 @@
 == Proposed Solution ==
 
- * Providers which don't support multiple schemas, should report an empty schema, all their content lives in that single schema ( ie was default).
- * Providers which have native schemas with multiple real schemas, should represent those available schemas to GetSchemas unless over-ridden
-in the connection string or by custom mappings.
- * The tables in the user schema are listed in empty schema (default) conceptually potentially twice.
+ * Providers which don't support multiple schemas, should report the parent folder name, all their content lives in that single schema ( ie was default).
+ * Providers which have native schemas with multiple real schemas, should represent those available schemas to GetSchemas unless over-ridden in the connection string or by custom mappings.
+ * The tables in the user schema or single folder are exposed via an empty schema (default).
  * Class names for databases are normally tablename, unless qualified which then has ~COLUMN_NAME appended. (if the are multiple geometries, FDO requires to know which one is the identifier)
  * Class names for file based providers is based on their file name as current
- * Therefore, The empty schema ":watercourses" could be also just "watercourses"
+ * Therefore, The empty schema ":watercourses" could be also just "watercourses" 
 
 which would result in
 
- * OSGEO.SHP returns filename
- * OSGEO.Gdal returns filename
+ * OSGEO.SHP returns filename (or dir:filename)
+ * OSGEO.Gdal returns filename  (or dir:filename)
+ * OSGEO.OGR returns filename (or dir:filename)
  * KingOracle returns schema:tablename or if connected as "schema" then just tablename
- * OSGEO.OGR returns filename
  * MySql returns schema:tablename or if connected as "schema" then just tablename
  * SDF still returns what ever you like as a schema name