Hi dev's, We currently use a lot transaction groups (the thing hidden in project properties) [0], so that triggers do their job on the fly and all layers are refreshed together on each edit action, without having to manually save edits and refresh maps.
This works very well, but sometimes we want to trigger procedures on DB's side and we are forced to some hack by adding attribute tables and inserting fake feature in it to trigger what we need (such as disconnect objets, cut features, refresh some views, ..) Is there a way to access the current transaction group from a layer in a python layer action so that we could avoid using those fake tables? I would like to simply reuse the current postgres connection to do some "select my_special_function([my _args]); " If we have a way to do that, that would allow QGIS to be a client for in-DB service-oriented architectures. Thanks for your lights ! All the best, Régis regis.haubo...@oslandia.com [0] http://qgis.org/en/site/forusers/visualchangelog214/#feature-transaction-groups-for-postgres-editing
_______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
