Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • Portal API Backend Portal API Backend
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 24
    • Issues 24
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Kontr 2.0Kontr 2.0
  • Portal API BackendPortal API Backend
  • Issues
  • #57

Review Items should be versioned (each change should create new version)

Review Items should be versioned.

Data that can be changed:

  • line begin, end

  • content

  • There should be - deteled_at, updated_at, created_at, author (the user who made a change)

It would be good to take a look at this extesion for the SQLAlchemy: https://github.com/kvesteri/sqlalchemy-continuum

SOURCES: https://docs.sqlalchemy.org/en/latest/orm/versioning.html https://blog.jondh.me.uk/2011/11/relational-database-versioning-strategies

Assignee
Assign to
Time tracking