-
Notifications
You must be signed in to change notification settings - Fork 715
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
AUTO-VACUUM or not? #646
Comments
In many cases JavaScript app authors do not consider memory & disk resource management at the earliest prototyping & delivery stages. I would highly favor enabling auto-vacuum by default in the next major (if not minor) release to deal with these cases. An excellent resource about auto-vacuum on Android: http://stackoverflow.com/questions/25135463/where-we-need-use-vacuum According to http://www.sqlite.org/pragma.html#pragma_auto_vacuum there are some tricks needed to enable auto-vacuum on existing sqlite database files. An alternative may be to make this more explicit by introducing a mandatory setting in the next major release. |
From http://www.sqlite.org/pragma.html#pragma_auto_vacuum with bold emphasis added to a few relevant items:
So if no form of VACUUM or AUTO-VACUUM is used:
I hope to document this sometime later. |
Unfortunately the DRAFT https://www.w3.org/TR/webdatabase/ does not explicitly deal with manual VACUUM vs AUTO-VACUUM. The following sections may be relevant:
https://www.w3.org/TR/webdatabase/#sensitivity-of-data:
https://www.w3.org/TR/webdatabase/#disk-space:
I found the following resources from a quick search:
The following resources describe the various AUTO-VACUUM options:
I would personally favor FULL AUTO-VACUUM since it seems to avoid indeterminate interruptions and (along with #645: secure delete) keep things cleaned up in general.
Another idea would be to make this an openDatabase option.
The text was updated successfully, but these errors were encountered: