-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Database size on status page #3759
Database size on status page #3759
Conversation
I think this is very messy what you're doing here. You're trying to use asynchronous features synchronously and creating a lot of weight for something that really doesn't need to be that complicated. See the new utility method I have provided for this. I suggest completely reworking this PR to just use that: 53507c7 |
Thanks you so much. |
Thanks for the guidance. |
@Navid200 What is the use-case that benefit of knowing database size? |
@olorinmaia If you have been using xDrip for years, the database may contain data you will never need inside xDrip any longer. Keeping data in xDrip corresponding to 20 years ago is not necessary. I welcome suggestions as to what could be the cause of this: #1280 Being able to see the size of the database can be useful for deciding when you may want to do some cleanup. |
Thanks for some info regarding this. If database cleaning is necessary, is this the way or is there other methods? |
Thanks for that link. I will need to update that. Yes, setting glucose retention to a value like 365 is a way to limit the size. |
This PR adds a new item to classic status page, the database size.
It removes the phrase "downgradable to" from the same status page.