Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • Project Forum Project Forum
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 104
    • Issues 104
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 13
    • Merge requests 13
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • EIPEIP
  • Project ForumProject Forum
  • Project ForumProject Forum
  • Issues
  • #434
Closed
Open
Issue created Jul 21, 2022 by Taico Aerts@taicoaertsOwner

Purge migrations and update schema

There are a lot of migrations which can no longer be applied. We should purge the migrations and update the schema with the current state of production. Here we should also add limits as those are present in MySQL but not in SQLite. This would ensure that production errors with the database are more likely to also show in development.

For the timing of this, this needs to be synced to occur after a release to production and this has been confirmed to be stable. The last few migrations can be kept.

Edited Jul 21, 2022 by Taico Aerts
Assignee
Assign to
Time tracking