cms-dev / cms-dev/cms

Database checker and fixer

Open
#634 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1k
Forks
412
Avg merge
6d 10h
Merged PRs (30d)
3

Description

I'd like to have a tool to check for consistence of database. This tool should check if the files are accessible and offer for a fix (replace it with an empty file, remove the submission, etc), maybe other things too.

This is the problem I came across: I was doing a DumpExport to migrate the database. The DumpExport found some inconsistency in the database. More specifically, some files got deleted (I created another issue explaining this: #635). The thing is that this error only appeared when trying to read the file, which was two hours after starting the DumpExport. I managed to fix it altering the database manually, but it was not the only corrupt file. So to correct each file I have to run the DumpExport, wait two hours so I can see the problem, correct it, and run again. This is not convenient.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the DumpExport workflow and issue #635 for the reported missing-file inconsistency. Determine where database records reference files and how DumpExport currently discovers failures. Done means a checker can identify inaccessible files before or independently of a long export and offer the proposed repair choices.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend, databases
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.