Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[OGR provider] Do not corrupt values when updating a GPKG feature #43311

Merged
merged 1 commit into from
May 24, 2021

Conversation

rouault
Copy link
Contributor

@rouault rouault commented May 20, 2021

and that the fid value is included in the fields to update, and that it
doesn't change.

Also rollback all changes if an update of FID is attempted.

Fixes #42274

@rouault rouault added Bug Either a bug report, or a bug fix. Let's hope for the latter! backport release-3_16 labels May 20, 2021
@github-actions github-actions bot added this to the 3.20.0 milestone May 20, 2021
and that the fid value is included in the fields to update, and that it
doesn't change.

Also rollback all changes if an update of FID is attempted.

Fixes qgis#42274
@Saijin-Naib
Copy link

Even, thank you so much for looking at this!

@nyalldawson
Copy link
Collaborator

rollback all changes if an update of FID is attempted.

Does this mean users can no longer manually modify fids? Or is this only in the case that an error occurs?

@rouault
Copy link
Contributor Author

rouault commented May 21, 2021

Does this mean users can no longer manually modify fids? Or is this only in the case that an error occurs?

It was already impossible to modify the FID in the Geopackage case, but no error was returned to the caller.

@nyalldawson nyalldawson merged commit f16c28b into qgis:master May 24, 2021
@qgis-bot
Copy link
Collaborator

The backport to release-3_16 failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-release-3_16 release-3_16
# Navigate to the new working tree
cd .worktrees/backport-release-3_16
# Create a new branch
git switch --create backport-43311-to-release-3_16
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick 09caca9312ae4e32314d2c28ad1c28295e1999d1
# Push it to GitHub
git push --set-upstream origin backport-43311-to-release-3_16
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-release-3_16

Then, create a pull request where the base branch is release-3_16 and the compare/head branch is backport-43311-to-release-3_16.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter!
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Data Corruption: Failed GPKG OID/FID Over-write causes value to spill into next attribute column
4 participants