An error occurred fetching the project authors.
  1. 30 Jul, 2018 1 commit
  2. 14 May, 2018 1 commit
  3. 20 Apr, 2018 1 commit
  4. 19 Apr, 2018 1 commit
  5. 18 Nov, 2017 1 commit
  6. 13 Nov, 2017 2 commits
  7. 11 Nov, 2017 2 commits
  8. 20 Sep, 2017 1 commit
  9. 07 Aug, 2017 1 commit
  10. 02 Aug, 2017 1 commit
  11. 27 Jul, 2017 2 commits
  12. 07 Jul, 2017 1 commit
  13. 21 Jun, 2017 1 commit
  14. 16 Jun, 2017 1 commit
  15. 29 May, 2017 1 commit
  16. 07 Apr, 2017 1 commit
  17. 24 Mar, 2017 1 commit
  18. 23 Feb, 2017 2 commits
  19. 26 Jan, 2017 1 commit
  20. 15 Dec, 2016 1 commit
  21. 02 Dec, 2016 1 commit
  22. 23 Nov, 2016 1 commit
  23. 30 Sep, 2016 1 commit
  24. 27 Sep, 2016 1 commit
  25. 09 Aug, 2016 1 commit
  26. 12 Jul, 2016 1 commit
  27. 03 Jun, 2016 2 commits
  28. 16 May, 2016 2 commits
    • Sean McGivern's avatar
      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.
      e8058bd2
    • Sean McGivern's avatar
      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).
      750b2ff0
  29. 09 May, 2016 1 commit
  30. 05 May, 2016 1 commit
  31. 17 Mar, 2016 1 commit
  32. 11 Mar, 2016 1 commit
  33. 07 Mar, 2016 1 commit
  34. 08 Feb, 2016 1 commit