Skip to content

backend really needs database #180

Open
@nikromen

Description

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

Activity

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

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    • Status

      In 2 years

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions