Read about our upcoming Code of Conduct on this issue

  1. 06 Jul, 2017 1 commit
    • Yorick Peterse's avatar
      Add many foreign keys to the projects table · 8b8987deee58
      Yorick Peterse authored
      This removes the need for relying on Rails' "dependent" option for data
      removal, which is _incredibly_ slow (even when using :delete_all) when
      deleting large amounts of data. This also ensures data consistency is
      enforced on DB level and not on application level (something Rails is
      really bad at).
      
      This commit also includes various migrations to add foreign keys to
      tables that eventually point to "projects" to ensure no rows get
      orphaned upon removing a project.
      8b8987deee58
  2. 05 Jul, 2017 3 commits
  3. 04 Jul, 2017 1 commit
  4. 03 Jul, 2017 3 commits
  5. 30 Jun, 2017 3 commits
  6. 29 Jun, 2017 2 commits
  7. 28 Jun, 2017 8 commits
  8. 26 Jun, 2017 1 commit
  9. 23 Jun, 2017 3 commits
  10. 21 Jun, 2017 1 commit
  11. 19 Jun, 2017 2 commits
  12. 16 Jun, 2017 2 commits
    • Pawel Chojnacki's avatar
      Move Prometheus service to project model · 41ea5ad13c4c
      Pawel Chojnacki authored
      41ea5ad13c4c
    • Yorick Peterse's avatar
      Refactor Project.with_feature_available_for_user · cfe62efd6b28
      Yorick Peterse authored
      This method used to use a UNION, which would lead to it performing the
      same query twice; producing less than ideal performance. Further, in
      certain cases ActiveRecord could get confused and mess up the variable
      bindings, though it's not clear how/why exactly this happens.
      
      Fortunately we can work around all of this by building some of the WHERE
      conditions manually, allowing us to use a simple OR statement to get all
      the data we want without any of the above problems.
      cfe62efd6b28
  13. 08 Jun, 2017 2 commits
  14. 05 Jun, 2017 1 commit
  15. 03 Jun, 2017 1 commit
  16. 02 Jun, 2017 1 commit
  17. 31 May, 2017 2 commits
  18. 30 May, 2017 3 commits