[geogig-dev] Issue in export-diff functionality

[Victor Olaya <volaya@xxxxxxxxxxxxxxxx>]

Hi

I think I have found a problem with the geopackages exported by the
export-diff endpoint, and would like to check with you beofre opening
a ticket, in case i am missing something.

Here is my test case:

I create a new commit in which I add a feature. If then i export the
diff introduced by that commit, i get a geopackage with the added
feature, and the fid mappings are in there correctly added for that
new feature. That is all fine.

Now i create a commit which removes a feature. The corresponding table
with features is empty, since it is not needed. An entry in the
changes table is added, and that is enough, since with the geogigid of
the deleted feature i can perform that change and update my local
layer. The table with mapping fids is also empty. This is also fine

If I now ask export-diff to provide the difference of that commit but
reversed, here is where the problem arises. The feature removal is now
an addition. This is reflected in the changes table, but the mappings
table and the data table are empty, so there is not enough data to
describe the change and apply it to update a local layer.

A bit more of testing, and it seems that the changes tables takes into
account the order of commits passed to create the diff, while the
other two tables (the one with feature data and the one with mappings)
are always the same, no matter which order is used.

Any ideas?

Thanks!




-- 
Victor Olaya
Software Engineer | Boundless
volaya@xxxxxxxxxxxxxxxx
@boundlessgeo