Enrico, I will try to see what’s going on and if I find some evidences I will put it in the issue tracker.
Didier > Le 20 juil. 2015 à 16:26, Enrico Ferreguti <[email protected]> a écrit : > > It's difficult to realize what happens from your description. The plugin is > very simple, it saves all buffer and restores them checking data consistency, > so the issues you report makes me think it could happen a featureId mismatch. > Perhaps you are trying to restore a version on a already modified layer. Did > you get some messages loading version file? Is it the same with non PostGis > Layers? > The plugin has been marked as experimental because it's not wide tested and I > fear it could bring to data losses, so I ask you to contribute reporting the > bug to the issue tracker (https://github.com/enricofer/layerVersion/issues > <https://github.com/enricofer/layerVersion/issues>), providing all the > informations (operational steps, sample datasets) needed to replicate the > issue. > Thanks. > > > > 2015-07-20 14:39 GMT+02:00 didier peeters <[email protected] > <mailto:[email protected]>>: > I’m facing a strange behavior now: I tested the layerVersion plugin, at first > it seemed to work fine and effectively bring back the previous polygon’s > shape. > But then a confusion appeared between the polygons : when moved one, it > would ‘disappear’ and another would move as well and after saving this only > the second polygon had moved while the first one would ‘re-appear’ at its > original place. When selecting a polygon, 2 more ones are selected as well, > and when deleting ‘them’ (with the red garbage can, I use QGis 2.8.2) the > first one disappears only. This behavior continues after having uninstalled > LayerVersion and restarted QGis. > > Is this a bug generated by LayerVersion ? Has anybody seen this before ? > My layer is provided by PostGis. > > > Didier > > >> Le 20 juil. 2015 à 13:24, Enrico Ferreguti <[email protected] >> <mailto:[email protected]>> a écrit : >> >> mmm... sorry, debug infos left in the code.... >> simply remove line 142 (the last) of file >> "/Users/didier/.qgis2/python/plugins/layerVersion/layerversion.py" >> with a text editor and reload the plugin. >> >> Regards. >> Enrico >> >> 2015-07-20 13:05 GMT+02:00 Matthias Kuhn <[email protected] >> <mailto:[email protected]>>: >> Hi, >> >> I remember geogig (formerly geogit) offers promising concepts for filebased >> spatial data management with historization and branching. >> Unfortunately I don't know the current status of the project and the >> progress of integration in QGIS. >> >> Matthias >> >> >> On 07/20/2015 11:25 AM, Neumann, Andreas wrote: >>> Hi Didier, >>> >>> I don't think that anyone is working on a client-side historisation option >>> in QGIS. And there wasn't much demand for that in the past, since most >>> serious GIS data resides in databases. >>> >>> Andreas >>> >>> On 2015-07-20 09:45, didier peeters wrote: >>> >>>> Hello Andreas, >>>> >>>> yes it's for some 'historisation', more precisely to make a filiation, and >>>> yes I certainly will use triggers in PostGIS. But I wanted to avoid >>>> confusion between different kind of edition operations that I'm not >>>> currently foreseeing; I'm not sure it will always be easy to distinct this >>>> specific action from others. And I thought that it might also be >>>> interesting outside of the database world, to have that "edit and >>>> preserve" operation. >>>> >>>> Didier >>>> >>>> Le 20 juil. 2015 à 09:10, Neumann, Andreas <[email protected] >>>> <mailto:[email protected]>> a écrit : >>>> Hi Didier, >>>> >>>> Is this for historisation purposes? If yes, I would look into database >>>> solutions to do historization. >>>> >>>> The SQL-MM standard has this as a built-in tool set for databases, >>>> however, PostgreSQL does not implement this part of the SQL specification >>>> (I believe the latest versions of SQL server and Oracle 12 does). However, >>>> you can simulate the same in Postgis, using triggers and rules. >>>> >>>> Andreas >>>> >>>> On 2015-07-20 08:00, didier peeters wrote: >>>> >>>> Hello, >>>> >>>> I would like to find the best solution to the following case: >>>> >>>> in QGis, when editing a polygon (splitting it in 2 parts) I need to save >>>> the original shape, in order to keep the different steps of its evolution; >>>> this operation is likely to be repeated several times. The solution I >>>> found is to >>>> start by copying the polygon, >>>> then edit it (split) >>>> then pasting back the original one, >>>> then adjust and update the attributes of the 2 new polygons. >>>> >>>> Is there a less tricky way to achieve this ? >>>> >>>> If not it would be nice to have an option in the save dialog (with a >>>> default behaviour set in the Settings), and I would file a feature >>>> request. >>>> >>>> Didier >>>> >>>> _______________________________________________ >>>> Qgis-user mailing list >>>> [email protected] <mailto:[email protected]> >>>> http://lists.osgeo.org/mailman/listinfo/qgis-user >>>> <http://lists.osgeo.org/mailman/listinfo/qgis-user> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Qgis-user mailing list >>>> [email protected] <mailto:[email protected]> >>>> http://lists.osgeo.org/mailman/listinfo/qgis-user >>>> <http://lists.osgeo.org/mailman/listinfo/qgis-user> >>> >>> >>> >>> _______________________________________________ >>> Qgis-user mailing list >>> [email protected] <mailto:[email protected]> >>> http://lists.osgeo.org/mailman/listinfo/qgis-user >>> <http://lists.osgeo.org/mailman/listinfo/qgis-user> >> >> _______________________________________________ >> Qgis-user mailing list >> [email protected] <mailto:[email protected]> >> http://lists.osgeo.org/mailman/listinfo/qgis-user >> <http://lists.osgeo.org/mailman/listinfo/qgis-user> >> > >
_______________________________________________ Qgis-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-user
