qgib
commented
6 years ago Author Name: Giovanni Manghi (@gioman)
QGIS 2.18:
add a postgis layer put it in off-line mode edit it (add feature) > is NOT asked to fill (not mandatory) the field that represent the PK in pgsql synchronize it back > all OK (the new feature is given a proper value for the PK field)
QGIS 3.4:
add a postgis layer put it in off-line mode (spatialite or geopackage) edit it (add feature) > the field that represent the PK is marked as mandatory and the user must fill it manually to be able to synchronize back. This of course can cause errors.
To the original issuer: I don't understand your description when using GPKG as format (I didn't tested your data because is not just a table, but it wants to restore a number of other things, like pgrouting). Here in my test if does indeed add a new field "fid", but in off line mode this is set as "autogenerate" and it does disappear when synchronizing back (and all the other columns are just ok).
- regression was changed from 0 to 1
- subject was changed from Check out with QGIS against a postgis database. to Off-Line editing should NOT ask to fill manually the PK field
- status_id was changed from Open to Feedback
- priority_id was changed from Normal to High
- operating_system was changed from Windows 10, Ubuntu 18.04 to
- crashes_corrupts_data was changed from 1 to 0
Author Name: Randal Hale (@rjhale1971) Original Redmine Issue: 20276 Affected QGIS version: 3.4.0 Redmine category:c++_plugins/offline_editing Assignee: David Signer
New description: On the checkout - If I use Geopackage I get a "shift" of attributes. I have included a screenshot named Pre-Checkout.png . When I check out the data the attributes move one column to the right. I included a screenshot for postcheckout.png. If you look at the two screenshots - all the attributes have moved columns.
28097-2
Old description:
I have a postgis database and the client is wanting to use the offline editing functionality. When I checkout a layer into a geopackage in 3.4 I noticed that there is a fid column added - but in adding the column it's shoving all the attribution over one column so the attribute no longer matches the column (for instance seg_side should contain either 'L' or 'R' and doesn't now).
If I take a layer offline into spatialite I'm having to manually fill out the primary key BUT the layer columns stay intact. Which manually filling out that is going to screw up the database on check-in.
I didn't try this in 3.2. I may try shortly if I get some time. So I have no idea if this is a regression or not.
I have attached a link to the original database in case something can be wrong there. It's a pd_dump and is 24mb so I've placed it in Dropbox: https://www.dropbox.com/s/67z5dn196497bev/hc911.backup?dl=0. It can be restored using psql -d -f hc911.backup
Related issue(s): #28122 (relates) Redmine related issue(s): 20301