I used to frequently get errors when copying and pasting features across geopackage files. So now, before saving the edited file, I select all features and set the fid to NULL, which avoid errors most of the times.
On Fri, Mar 20, 2020 at 5:07 AM Alexis R.L. <[email protected]> wrote: > Greetings, > > Personnally when splitting layers and when there are FID conflits, I try > to solve it manually. Sometimes it tells me that the fid of feature x > cannot be change, which are not indistinguishable. > > And the next time you open the geopackage there is a change that the fid > column will now be the next column over and the initial fid column with bad > fids is still there. If you had critical information in your second column > too bad, its now a fid and you lost that information forever. > > Maybe that issue was fixed already since I'm mostly using 3.4.4 on my main > setup as of now (waiting for some PRs to get merged before updating). > > Thanks > > Alex > > > Le jeu. 19 mars 2020 à 02:04, Nyall Dawson <[email protected]> a > écrit : > >> Hi list, >> >> Just wondering what everyone's thoughts are about geopackage FID >> columns. Personally, I find them an absolute nightmare to deal with, >> resulting in annoying (and dangerous) issues when trying to save >> geopackage edits, such as >> - field type issues: converting certain formats to geopackage fails, >> because existing fields with name "fid" are of an incompatible type >> with geopackage. Solution: manually uncheck the "fid" field from the >> "save as" dialog. >> - unique constraint violations: we've mostly fixed this in processing, >> but it's still unfortunately really common to get failures when saving >> edits to geopackage because some operation has resulted in duplicate >> fids. This can be a nightmare to fix, if it's even possible to do so. >> >> I personally HATE HATE HATE these columns, and would rather I never >> saw them ever again. Does anyone else feel the same? If so, could we >> potentially just permanently hide these columns from QGIS and avoid >> all these dangerous issues for users? >> >> Nyall >> _______________________________________________ >> QGIS-Developer mailing list >> [email protected] >> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer >> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer > > _______________________________________________ > QGIS-Developer mailing list > [email protected] > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
_______________________________________________ QGIS-Developer mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
