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

Safer Stream Deletion #4495

Closed
wixbot opened this issue Aug 9, 2014 · 1 comment
Closed

Safer Stream Deletion #4495

wixbot opened this issue Aug 9, 2014 · 1 comment
Assignees
Milestone

Comments

@wixbot
Copy link

wixbot commented Aug 9, 2014

When deleting a stream from a database, we currently do it right away, before the database has committed. If we were to end up not being able to commit the database changes (power loss / network disconnection / remote changed before we could commit, etc.), that stream would be lost forever. The proper solution is to delay stream deletes until after we are sure we committed the database.

Originally opened by mike-gc

@wixbot
Copy link
Author

wixbot commented Sep 3, 2014

Originally changed by mike-gc
Resolution set to Fixed
Status changed from Open to Resolved

@wixbot wixbot added this to the v4.0 milestone Dec 20, 2015
@wixbot wixbot closed this as completed Dec 20, 2015
@rseanhall rseanhall modified the milestones: v4.0, SettingsBrowser Nov 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants