From 94530040add3e349e45470f61c8152648da14753 Mon Sep 17 00:00:00 2001 From: Hunter Long Date: Fri, 18 Sep 2020 23:53:28 -0700 Subject: [PATCH] Updated Issues and Solutions (markdown) --- Issues-and-Solutions.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/Issues-and-Solutions.md b/Issues-and-Solutions.md index d12392a..01f42c2 100644 --- a/Issues-and-Solutions.md +++ b/Issues-and-Solutions.md @@ -17,4 +17,9 @@ If you notice a database error during migration, you can reset your Statping ins - In your Statping directory (contains config.yml) run command: `statping export`. This will export all elements into a timestamped JSON file. This file will not include previous hits or failures. - Delete `assets` folder if you have one. - Delete and Recreate MySQL, Postgres database, or delete `statping.db`. -- Import previous data by running: `statping import backup.json` (replace backup.json with your exported filename) \ No newline at end of file +- Import previous data by running: `statping import backup.json` (replace backup.json with your exported filename) + +## Deleting Old Records + +- `DELETE FROM hits WHERE created_at < '2020-02-21 00:00:00';` // Delete hits older than +- `DELETE FROM failures WHERE created_at < '2020-02-21 00:00:00';` // Delete failures older than \ No newline at end of file