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
  • gitlab-ce
  • lib
  • api
  • v3
  • github.rb
Find file BlameHistoryPermalink
  • Yorick Peterse's avatar
    Move read_only/read_write back to Gitlab::Database · bc197247
    Yorick Peterse authored Jul 29, 2021
    These methods were scoped to a connection in
    https://gitlab.com/gitlab-org/gitlab/-/merge_requests/65262. A
    discussion after the merge request was merged revealed these methods
    aren't tied to a specific connection, and as such better belong in
    Gitlab::Database.
    
    I briefly considered moving them to the Gitlab module instead, as the
    methods don't actually run any database queries. Unfortunately, this
    isn't possible as this module is loaded too early to prepend it with an
    EE module.
    bc197247
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7