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

Avoid accidentally overwriting Geopackage database when creating new layer #32823

Closed
huber-j opened this issue Nov 13, 2019 · 1 comment · Fixed by #34817
Closed

Avoid accidentally overwriting Geopackage database when creating new layer #32823

huber-j opened this issue Nov 13, 2019 · 1 comment · Fixed by #34817
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! GUI/UX Related to QGIS application GUI or User Experience

Comments

@huber-j
Copy link

huber-j commented Nov 13, 2019

When creating a new Geopackage layer and selecting an existing gpkg file, QGIS asks if the gpkg database should be overwritten or if the new layer should be added to the existing database. Although adding the layer is the default, it easily happens that someone accidentally clicks on the wrong button and overwrites an existing database with many layers.
It would be good if QGIS would display an additional dialog box "You are about to overwrite a database containing x layers with y features - are you shure? [Overwrite data | Cancel]" when "overwrite" is selected.

An alternative would be to remove the option to overwrite the database and replace the current dialog by a status message "New Layer is being added to existing database".
This would make overwriting an existing database an explicit action which requires deleting the old gpkg file first.

@uclaros
Copy link
Contributor

uclaros commented Feb 28, 2020

This is very important and should be filed as a bug, not a feature request! The potential for data loss is huge! It's also there when exporting a layer, a quite common operation.
We can't have a Overwrite File button right next to the Overwrite Layer button and not ask for confirmation nor warn about the consequences. Not on database formats.

@elpaso elpaso added Bug Either a bug report, or a bug fix. Let's hope for the latter! GUI/UX Related to QGIS application GUI or User Experience and removed Feature Request labels Feb 28, 2020
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! GUI/UX Related to QGIS application GUI or User Experience
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants