No that was not my intention. I don't mind if it depends on another core plugin, that is actually good
If I remember right, I reused that lib because it was also part of core or of some other plugin, and I found the DB manager architecture to be more complex and not inmediate for being used as a lib. But yes, I guess all can be done as well with the DB manager classes I wouldn't be against it if someone wants to modify the algorithms that use postgis_utils and use DB manager code instead, so we can get rid of a library and not have redundant code... Cheers! 2015-10-09 9:31 GMT+02:00 kimaidou <[email protected]>: > Hi Spencer, > > When I created these script, I think the postgis_utils did not exist yet (or > I just did not know about it). And I thought all the work around Databases > was focused on DBManager to avoid redundacy. > > We should ask Victor about it. Perhaps Victor did not want processing to > depend on another plugin ? > > Cheers > Michaël > > 2015-10-08 20:45 GMT+02:00 Spencer Gardner <[email protected]>: >> >> Brilliant. I wasn't aware that it was so easy to use DB Manager from >> Python. Up to now I've been connecting to my PostGIS database using the >> postgis_utils included with Processing. >> >> So this begs the question: what is the use of postgis_utils if the same >> functionality is achieved through DB Manager? >> >> _______________________________________________ >> Qgis-developer mailing list >> [email protected] >> http://lists.osgeo.org/mailman/listinfo/qgis-developer > > > > _______________________________________________ > Qgis-developer mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/qgis-developer _______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
