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.

Sign up for GitHub

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

Jump to bottom

Workaround for possible Android data loss (193) should be after every write #672

Open
brodycj opened this issue Apr 20, 2017 · 0 comments
Open

Workaround for possible Android data loss (193) should be after every write #672

brodycj opened this issue Apr 20, 2017 · 0 comments
Labels
bug-data-loss-risk bug-general

Comments

@brodycj
Copy link
Contributor

brodycj commented Apr 20, 2017 •
edited
Loading

Related to #193 (data loss on certain Android versions when using android.database.sqlite implementation, optional workaround already added) and #671 (safer Android defaults):

The optional workaround for #193 is to close and reopen the database after every COMMIT. This workaround should be applied after every write, if enabled.

ADDITIONAL NOTE: I expect to fix this while fixing #671 (safer Android defaults).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug-data-loss-risk bug-general
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@brodycj