BigW Consortium Gitlab

  1. 18 Nov, 2017 1 commit
  2. 13 Nov, 2017 2 commits
  3. 11 Nov, 2017 2 commits
  4. 20 Sep, 2017 1 commit
  5. 07 Aug, 2017 1 commit
  6. 02 Aug, 2017 1 commit
  7. 27 Jul, 2017 2 commits
  8. 07 Jul, 2017 1 commit
  9. 21 Jun, 2017 1 commit
  10. 16 Jun, 2017 1 commit
  11. 29 May, 2017 1 commit
  12. 07 Apr, 2017 1 commit
  13. 24 Mar, 2017 1 commit
  14. 23 Feb, 2017 2 commits
  15. 26 Jan, 2017 1 commit
  16. 15 Dec, 2016 1 commit
  17. 02 Dec, 2016 1 commit
  18. 23 Nov, 2016 1 commit
  19. 30 Sep, 2016 1 commit
  20. 27 Sep, 2016 1 commit
  21. 09 Aug, 2016 1 commit
  22. 12 Jul, 2016 1 commit
  23. 03 Jun, 2016 2 commits
  24. 16 May, 2016 2 commits
    • Return a relation with Postgres · e8058bd2
      Sean McGivern authored
      Postgres only needs to select a single column, so that can used as a
      sub-query where `Milestone.upcoming_ids_by_projects` is actually used in
      `IssuableFinder`.
      
      MySQL needs to select the `due_date` column because it's used in the
      `HAVING` clause, so it has to return an array of IDs.
    • Make upcoming milestone work across projects · 750b2ff0
      Sean McGivern authored
      Before: we took the next milestone due across all projects in the
      search and found issues whose milestone title matched that
      one. Problems:
      
      1. The milestone could be closed.
      2. Different projects have milestones with different schedules.
      3. Different projects have milestones with different titles.
      4. Different projects can have milestones with different schedules, but
         the _same_ title. That means we could show issues from a past
         milestone, or one that's far in the future.
      
      After: gather the ID of the next milestone on each project we're looking
      at, and find issues with those milestone IDs. Problems:
      
      1. For a lot of projects, this can return a lot of IDs.
      2. The SQL query has to be different between Postgres and MySQL, because
         MySQL is much more lenient with HAVING: as well as the columns
         appearing in GROUP BY or in aggregate clauses, MySQL allows them to
         appear in the SELECT list (un-aggregated).
  25. 09 May, 2016 1 commit
    • Remove the annotate gem and delete old annotations · f1479b56
      Jeroen van Baarsen authored
      In 8278b763 the default behaviour of annotation
      has changes, which was causing a lot of noise in diffs. We decided in #17382
      that it is better to get rid of the whole annotate gem, and instead let people
      look at schema.rb for the columns in a table.
      
      Fixes: #17382
  26. 05 May, 2016 1 commit
  27. 17 Mar, 2016 1 commit
  28. 11 Mar, 2016 1 commit
  29. 07 Mar, 2016 1 commit
  30. 08 Feb, 2016 1 commit
  31. 09 Dec, 2015 1 commit
  32. 19 Oct, 2015 1 commit
    • Improve performance of sorting milestone issues · 4ff75e31
      Yorick Peterse authored
      This cuts down the time it takes to sort issues of a milestone by about
      10x. In the previous setup the code would run a SQL query for every
      issue that had to be sorted. The new setup instead runs a single SQL
      query to update all the given issues at once.
      
      The attached benchmark used to run at around 60 iterations per second,
      using the new setup this hovers around 600 iterations per second. Timing
      wise a request to update a milestone with 40-something issues would take
      about 760 ms, in the new setup this only takes about 130 ms.
      
      Fixes #3066
  33. 03 Oct, 2015 1 commit
  34. 22 Jun, 2015 1 commit