Changes between Version 5 and Version 6 of FDORfc43


Ignore:
Timestamp:
10/28/09 01:44:10 (15 years ago)
Author:
zspitzer
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • FDORfc43

    v5 v6  
    4949There is no need to inject provider names into the naming.
    5050
    51 PostGIS has been already meant updated following this mailing list discussion
    52 http://www.nabble.com/Is-there-a-Feature-class-naming-convention-to15021175s18162.html#a15021175
    53 http://trac.osgeo.org/fdo/ticket/310
    54 
     51The PostGIS provider has already adopted this approach following this mailing list discussion[[BR]]
     52[http://www.nabble.com/Is-there-a-Feature-class-naming-convention-to15021175s18162.html#a15021175][[BR]]
     53[http://trac.osgeo.org/fdo/ticket/310][[BR]]
    5554
    5655== Proposed Solution ==
    … …  
    6059in the connection string or by custom mappings.
    6160 * The tables in the user schema are listed in empty schema (default) conceptually potentially twice.
    62  * Class names for databases are normally tablename, unless qualified which then has ~COLUMN_NAME appended. (Coz if the are multiple geometries, FDO requires to know which one is the identifier)
     61 * 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)
    6362 * Class names for file based providers is based on their file name as current
    6463 * Therefore, The empty schema ":watercourses" could be also just "watercourses"