Hi , One drawback for Mapinfo switchers, is that they have to import data in sqlite or postgres to use DBManager / Qspatialite and similar plugins. They are not used to it, and it can be a bad pratice with a centrlized data store, since we have duplication of data.
I remember someone advertising here the new OGR SQL dialect described here [0]. It seems to support join and union operations, create index.. but in a limited way. When database are SQL enabled (sqlite, postgres... ), OGR dialect is overidden by destination database sql. RENAME, DROP, ADD column is also supported.. So, I'm wondering if we could imagine a native SQL window, working with whatever datasource in QGIS, but raising warnings when some SQL is limited, following datasources. We could also imagine a tool to manage data file structure (like table manager but for every OGR file) that really misses to QGIS. Has anyone sufficiently used OGR SQL to have an opinion on this? If yes, what obstacles do we have in front of us to achieve this? Cheers [0] http://www.gdal.org/ogr/ogr_sql.html <http://www.gdal.org/ogr/ogr_sql.html> -- View this message in context: http://osgeo-org.1560.n6.nabble.com/Advanced-SQL-Editor-in-QGIS-tp5043777p5043794.html Sent from the Quantum GIS - User mailing list archive at Nabble.com. _______________________________________________ Qgis-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-user
