Skip to content

Add note for purge service to explain behaviour #7874

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

Merged
merged 1 commit into from
Dec 16, 2018
Merged

Add note for purge service to explain behaviour #7874

merged 1 commit into from
Dec 16, 2018

Conversation

KarimGeiger
Copy link
Contributor

Description:

I recently thought my purge service did not work since there still were some entries in my database having a younger date than specified by the purge. It took me quite a while to find an answer as to why that is, so I thought adding a note to the documentation wouldn't hurt.

Source: https://community.home-assistant.io/t/recorder-does-not-purge/70077/2

Pull request in home-assistant (if applicable): n/a

Checklist:

  • Branch: next is for changes and new documentation that will go public with the next home-assistant release. Fixes, changes and adjustments for the current release should be created against current.
  • The documentation follows the standards.

I recently thought my purge service did not work since there still were some entries in my database having a younger date than specified by the purge. It took me quite a while to find an answer as to why that is, so I thought adding a note to the documentation wouldn't hurt.

Source: https://community.home-assistant.io/t/recorder-does-not-purge/70077/2
@ghost ghost added the to-do label Dec 16, 2018
Copy link
Member

@fabaff fabaff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks 🐦

@fabaff fabaff merged commit cf25959 into home-assistant:current Dec 16, 2018
@ghost ghost removed the to-do label Dec 16, 2018
@frenck frenck added enhancement current This PR goes into the current branch labels Dec 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
current This PR goes into the current branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants