Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • 12-9-stable
  • 12-7-stable
  • 12-6-stable
  • 12-8-stable
  • github/fork/Kloppi313/patch-1
  • 12-5-stable
  • 12-4-stable
  • github/fork/ramalokesh8477/master
  • 12-1-stable
  • 12-2-stable
  • 12-0-stable
  • 12-3-stable
  • 42-42-stable
  • github/fork/hussamgit398/patch-2
  • 12-3-auto-deploy-20190911
  • 12-3-auto-deploy-20190916
  • 12-3-auto-deploy-20190908
  • 12-3-auto-deploy-20190901
  • 12-3-auto-deploy-20190901-32664
  • v12.10.0.pre
  • v12.9.0
  • v12.9.0-rc42
  • v12.8.7
  • v12.8.6
  • v12.8.5
  • v12.8.4
  • v12.8.3
  • v12.6.8
  • v12.7.7
  • v12.8.2
  • v12.8.1
  • v12.9.0.pre
  • v12.8.0
  • v12.8.0-rc42
  • v12.5.10
  • v12.7.6
  • v12.6.7
  • v12.7.5
  • v12.5.9
40 results

merge_request_spec.rb

  • Sean McGivern's avatar
    39c9928c
    Fix N+1 in `MergeRequest#merge_request_diff_for` · 39c9928c
    Sean McGivern authored
    Previously, this would issue a query for each unique `diff_refs_or_sha`
    passed. This was because we didn't want to load other MR diffs into memory, as
    they had some very large columns.
    
    Now they are actually very small, and it's more efficient to just load them all
    at once and do the finding in Ruby.
    39c9928c
    History
    Fix N+1 in `MergeRequest#merge_request_diff_for`
    Sean McGivern authored
    Previously, this would issue a query for each unique `diff_refs_or_sha`
    passed. This was because we didn't want to load other MR diffs into memory, as
    they had some very large columns.
    
    Now they are actually very small, and it's more efficient to just load them all
    at once and do the finding in Ruby.