DB sanity command #35

Closed
opened 2021-10-25 09:43:05 +02:00 by mpeltriaux · 1 comment
Owner

Status quo

There is no command for checking on data sanity, yet.

To Do

We need a db_cleanup command which includes

  1. Remove of data where deleted was set x days ago -> finally delete them
  2. Remove of garbage data (related objects which might not have been cascade-deleted properly)

This command can then be run once a night using e.g. cron.

# Status quo There is no command for checking on data sanity, yet. # To Do We need a `db_cleanup` command which includes 1. Remove of data where `deleted` was set x days ago -> finally delete them 1. Remove of garbage data (related objects which might not have been cascade-deleted properly) This command can then be run once a night using e.g. cron.
mpeltriaux added the
enhancement
label 2021-10-25 09:43:05 +02:00
mpeltriaux self-assigned this 2021-10-25 09:43:05 +02:00
mpeltriaux referenced this issue from a commit 2021-11-17 09:32:18 +01:00
mpeltriaux referenced this issue from a commit 2021-11-17 09:32:18 +01:00
mpeltriaux referenced this issue from a commit 2021-11-17 14:33:07 +01:00
mpeltriaux referenced this issue from a commit 2021-11-17 14:33:07 +01:00
Author
Owner

Sanity command will be extended for each relevant use case in a new feature.

Sanity command will be extended for each relevant use case in a new feature.
btuelek referenced this issue from a commit 2024-12-05 13:18:36 +01:00
btuelek referenced this issue from a commit 2024-12-05 13:18:36 +01:00
btuelek referenced this issue from a commit 2024-12-05 13:18:36 +01:00
btuelek referenced this issue from a commit 2024-12-05 13:18:36 +01:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: IT-Naturschutz/konova#35
No description provided.