To keep the database under control I exclude a lot of entities from filling up the database with the recorder setting in config.
Have often been thinking, why isn`t it possible to also be able to do that in the gui (integration/device or entity (class) properties for example). A switch record values on/off would be very helpfull in my eyes.
Just never really been in the picture to do so, or any (practical) reasons why it is not (easily) possible to do?
Agree completely
I agree as well, moving it to the GUI like all the rest of the configuration is going - but may I suggest that if someone was to implement this, they include an option to delete all history for the object you no longer want to retain the history for.
A simple “I see [object] currently has [x number] historical records, do you wish to keep them?” type question with a yes or no response would be the simplest, and I wouldn’t mind even an “Are you sure?” double confirmation just to make certain you absolutely want to do it.
Right now it’s a painful process of making changes to the database which includes the inherent risks of making a change at that level.