You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using geodiff, it may happen that OGR (and therefore also QGIS) would report wrong feature counts. This is caused by the fact that OGR uses its own table gpkg_ogr_contents with feature counts for each table which are auto-updated by triggers. But when applying changesets with geodiff, we temporarily disable triggers and therefore the counts do not get updated.
This does not lead to any harm AFAIK, but it is very confusing for users to see incorrect feature counts in QGIS.
It would be good to handle this nicely - probably by not disabling these particular triggers, or by handling updates of this table in some other way.
The text was updated successfully, but these errors were encountered:
When using geodiff, it may happen that OGR (and therefore also QGIS) would report wrong feature counts. This is caused by the fact that OGR uses its own table
gpkg_ogr_contents
with feature counts for each table which are auto-updated by triggers. But when applying changesets with geodiff, we temporarily disable triggers and therefore the counts do not get updated.This does not lead to any harm AFAIK, but it is very confusing for users to see incorrect feature counts in QGIS.
It would be good to handle this nicely - probably by not disabling these particular triggers, or by handling updates of this table in some other way.
The text was updated successfully, but these errors were encountered: