add sql condition to not include unconfirmed fetches to the fetch history or statistics
Closes None
What does this MR do?
Many statistics and the fetch history include the unconfirmed slots. Currently, they are deleted from the table after a while. In this merge request, a check is added whether a slot is confirmed. Later, the deletion could be set to everything from the day before yesterday or such and later it might vanish fully.
How confident are you it won't break things if deployed?
(be honest!)
Links to related issues
Any relevant links (issues, documentation, slack discussions).
How to test
Steps a reviewer can take to verify that this MR does what it says it does e.g.
- Checkout branch locally
- Login as foodsaver
- ...
Screenshots (if applicable)
Any relevant screenshots if this is a design / frontend change
Checklist
-
added a test, or explain why one is not needed/possible... -
no unrelated changes -
asked someone for a code review -
joined #foodsharing-beta channel at https://slackin.yunity.org -
added an entry to CHANGELOG.md (description, merge request link, username(s)) -
Once your MR has been merged, you are responsible to update the #foodsharing-beta Slack channel about what has been changed here. They will test your work in different browsers, roles or other settings
Edited by Caluera