Changes between Version 2 and Version 3 of FDORfc45


Ignore:
Timestamp:
Dec 11, 2009, 11:52:06 AM (14 years ago)
Author:
oresthalustchak
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FDORfc45

    v2 v3  
    4848== Proposed Solution ==
    4949
    50 What we would like to do is complete our work to get a working PostGIS provider and then replace the current open source code with our new copy. Note that we plan to use native PostGIS schema without adding additional metadata tables just as the current provider does. It will be able to read any schemas created by the current version of the provider and itself will generate generic PostGIS schemas.
     50What we would like to do is complete our work to get a working PostGIS provider and then add it as a new PostGIS provider, keeping the existing one in place. The new provider will be called OSGeo.PostGISDB to distinguish it from the current OSGeo.PostGIS.
     51
     52Note that we plan to use native PostGIS schema without adding additional metadata tables just as the current provider does. It will be able to read any schemas created by the current version of the provider and itself will generate generic PostGIS schemas.
    5153
    5254This provider will support the requirements outlined in the initial PostGIS RFC: [http://trac.osgeo.org/fdo/wiki/FDORfc3]. The restriction of requiring only lower case class and property names will be lifted. Inheritance support will be added using native Postgres table inheritance.