[QGIS-Developer] Geopackage FID columns: i HATE them!!!!

[Nathan Woodrow]

I agree.

If there is an ID that is used internally as a unique primary key it should
never be shown to the user. It should not be expected to be edited outside
of the provider's control or be stable between edits.

If you need a stable ID for reference you should make your own {{insert
rant about people wanting to use increating ints as a reference ID}}

On Thu, Mar 19, 2020 at 4:04 PM Nyall Dawson <nyall.dawson at gmail.com> wrote:

> 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
> QGIS-Developer at lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20200319/f71e2726/attachment-0001.html>