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

Alerts should be stored in an SQLite database instead of in memory #30

Open
justdave opened this issue Aug 23, 2017 · 2 comments
Open
Assignees
Milestone

Comments

@justdave
Copy link
Owner

If you choose an entire state or the country, it's a big list of alerts at any given time. Save memory by storing it in a database instead. This also allows a lot of other features on the enhancement request list to be implemented easier (such as alert caching, and early dismissal of non-expired alerts)

@justdave justdave added this to the Version 2.0 milestone Mar 22, 2020
@justdave
Copy link
Owner Author

My MCStatus app already does this, we can probably lift some of the code from there (convert Java to Kotlin though)

@justdave justdave self-assigned this Dec 26, 2020
@justdave
Copy link
Owner Author

justdave commented Jan 4, 2021

alerts should be stored by widget, since different widgets can have different lists.
when a widgets is deleted, delete all entries in the DB that belong to that widget.
when our periodic timers fire, delete any expired alerts.

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

1 participant