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

cannot VACUUM from within a transaction #25975

Closed
qgib opened this issue Feb 12, 2018 · 7 comments
Closed

cannot VACUUM from within a transaction #25975

qgib opened this issue Feb 12, 2018 · 7 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! DB Manager Relating to the DB Manager core plugin Regression Something which used to work, but doesn't anymore

Comments

@qgib
Copy link
Contributor

qgib commented Feb 12, 2018

Author Name: Arjan Mossel (Arjan Mossel)
Original Redmine Issue: 18079
Affected QGIS version: master
Redmine category:db_manager


In the current version of QGIS 2.99 it is not possible to run VACUUM on a SQLite database. Error:

"cannot VACUUM from within a transaction"

Related:
https://bugs.python.org/issue28518
ghaering/pysqlite#109 with a workaround

@qgib
Copy link
Contributor Author

qgib commented Feb 12, 2018

Author Name: Nyall Dawson (@nyalldawson)


How do you trigger this error in QGIS? I've been unable to reproduce.


  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented Feb 13, 2018

Author Name: Arjan Mossel (Arjan Mossel)


I installed QGIS 2.99 (alongside 2.18) via osgeo4w-setup-x86_64.exe, on Windows 7. Currently at b6ad920 (updated yesterday).

I can reproduce it by doing "New SpatiaLite layer", creating a new database with a table with just a text field. Then opening this database in the Database Manager and doing "Run Vacuum" results in a popup with "cannot VACUUM from within a transaction".


  • status_id was changed from Feedback to Open

@qgib
Copy link
Contributor Author

qgib commented Feb 13, 2018

Author Name: Nyall Dawson (@nyalldawson)


  • regression was changed from 0 to 1

@qgib
Copy link
Contributor Author

qgib commented Feb 13, 2018

Author Name: Nyall Dawson (@nyalldawson)


Confirmed on Windows

@qgib
Copy link
Contributor Author

qgib commented Feb 14, 2018

Author Name: Nyall Dawson (@nyalldawson)


PR #6338


  • status_id was changed from Open to In Progress
  • pull_request_patch_supplied was changed from 0 to 1

@qgib
Copy link
Contributor Author

qgib commented Feb 16, 2018

Author Name: Nyall Dawson (@nyalldawson)


Applied in changeset 838bde3.


  • status_id was changed from In Progress to Closed
  • done_ratio was changed from 0 to 100

@qgib qgib closed this as completed Feb 16, 2018
@qgib
Copy link
Contributor Author

qgib commented Feb 21, 2018

Author Name: Giovanni Manghi (@gioman)


  • resolution was changed from to fixed/implemented

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! DB Manager Relating to the DB Manager core plugin Regression Something which used to work, but doesn't anymore labels May 25, 2019
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! DB Manager Relating to the DB Manager core plugin Regression Something which used to work, but doesn't anymore
Projects
None yet
Development

No branches or pull requests

1 participant