On Tue, Nov 23, 2010 at 7:08 PM, [email protected] <[email protected]> wrote: > Sounds great, but: > - it means duplicating work
Not really - the import should work with any vector layer (e.g. kml, spatialite, or even another postgis db) - so it would be a superset of the functionality, rather than a duplicate. > - it will to be kept in sync with upstream postgis changes I have the impression that postgis is backwards compatible, so no changes should be necessary until postgis 2.0 - please correct me if I'm wrong. > - it does not allow writing sql dumps, useful for users without direct > access to db. The sql would have to be generated anyway within qgis libraries, so that's just a matter of giving the user a chance to save the dump instead of executing it in the current connection. Martin _______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
