BigW Consortium Gitlab

  1. 07 Oct, 2016 1 commit
    • Add markdown cache columns to the database, but don't use them yet · e94cd6fd
      Nick Thomas authored
      This commit adds a number of _html columns and, with the exception of Note,
      starts updating them whenever the content of their partner fields changes.
      
      Note has a collision with the note_html attr_accessor; that will be fixed later
      
      A background worker for clearing these cache columns is also introduced - use
      `rake cache:clear` to set it off. You can clear the database or Redis caches
      separately by running `rake cache:clear:db` or `rake cache:clear:redis`,
      respectively.
  2. 30 Sep, 2016 1 commit
  3. 27 Sep, 2016 1 commit
  4. 01 Jul, 2016 1 commit
  5. 29 Jun, 2016 1 commit
  6. 03 Jun, 2016 2 commits
  7. 19 May, 2016 1 commit
  8. 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).
  9. 09 May, 2016 2 commits
  10. 06 May, 2016 1 commit
  11. 05 May, 2016 1 commit
  12. 21 Apr, 2016 3 commits
  13. 01 Apr, 2016 2 commits
  14. 23 Mar, 2016 1 commit
  15. 17 Mar, 2016 1 commit
  16. 12 Mar, 2016 3 commits
  17. 11 Mar, 2016 1 commit
  18. 07 Mar, 2016 1 commit
  19. 02 Mar, 2016 2 commits
  20. 22 Feb, 2016 1 commit
  21. 08 Feb, 2016 1 commit
  22. 03 Feb, 2016 1 commit
  23. 02 Feb, 2016 3 commits
  24. 08 Jan, 2016 1 commit
  25. 07 Jan, 2016 2 commits
  26. 05 Jan, 2016 1 commit
  27. 24 Dec, 2015 1 commit
  28. 03 Dec, 2015 1 commit