Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • G gitlab-ce
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • nexedinexedi
  • gitlab-ce
  • Repository
You need to sign in or sign up before continuing.
  • gitlab-ce
  • db
  • structure.sql
Find file BlameHistoryPermalink
  • Douglas Barbosa Alexandre's avatar
    Remove FK dast_site_profiles_builds.ci_build_id as we have LFK · 89d4d45e
    Douglas Barbosa Alexandre authored Jan 10, 2022
    In https://gitlab.com/gitlab-org/gitlab/-/merge_requests/77908 we
    already added a ["loose foreign key"](
    https://docs.gitlab.com/ee/development/database/loose_foreign_keys.html)
    to replace this foreign key. Now that this has been running fine in
    production we should be OK to remove the foreign key altogether.
    
    This was added in a post-deployment migration as we want to ensure that
    they have the correct code running with the loose foreign key in place
    before we remove the foreign key to ensure that there isn't any lost
    deletes.
    
    Changelog: other
    89d4d45e
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7