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.

Sign up for GitHub

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

Jump to bottom

backend really needs database #180

Open

nikromen opened this issue Oct 7, 2024 · 0 comments

Member

nikromen commented Oct 7, 2024

we discussed this at meetings like 4269x but nobody created an issue about it so we are successfully postponing it :D

because of that the directory schema and relations between reviews, results and results diffed by reviews are mess
we want:

to have results with unique ID (we currently don't since ID is name)
to have result - review relation
- have added parsed result according to review to it

^ This is done somehow inside the current directory structure with names as IDs (and reviews ids...) glued together.

we also want in the future implemented (and db will ease the implementation):

getting non-duplicated reviews if news are available

^ that's what I remember, if I forgot something, please edit this issue

fedora-copr-github-bot added this to CPT Kanban

github-project-automation bot moved this to Needs triage in CPT Kanban

nikromen moved this from Needs triage to In 2 years in CPT Kanban

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment