1. 16 11月, 2015 1 次提交
  2. 13 11月, 2015 1 次提交
  3. 06 11月, 2015 1 次提交
  4. 05 11月, 2015 1 次提交
  5. 03 11月, 2015 1 次提交
  6. 21 10月, 2015 2 次提交
  7. 20 10月, 2015 1 次提交
  8. 14 10月, 2015 2 次提交
  9. 08 10月, 2015 1 次提交
    • Y
      Revamp finding projects by namespaces · 03417456
      Yorick Peterse 提交于
      By using a JOIN we can remove the need for using 2 separate queries to
      find a project by its namespace. Combined with an index (only needed for
      PostgreSQL) this reduces the query time from ~245 ms (~520 ms for the
      first call) down to roughly 10 ms (~15 ms for the first call).
      03417456
  10. 06 10月, 2015 1 次提交
    • Y
      Revamp trending projects query · b7abba0c
      Yorick Peterse 提交于
      This changes the query to use a COUNT nested in an INNER JOIN, instead
      of a COUNT plus a GROUP BY. There are two reasons for this:
      
      1. Using a COUNT in an INNER JOIN can be quite a bit faster.
      2. The use of a GROUP BY means that method calls such as "any?"
         (and everything else that calls "count") operate on a Hash that
         counts the amount of notes on a per project basis, instead of just
         counting the total amount of projects.
      
      The query has been moved into Project.trending as its logic is simple
      enough. As a result of this testing the TrendingProjectsFinder class
      simply involves testing if the right methods are called, removing the
      need for setting up database records.
      b7abba0c
  11. 05 10月, 2015 1 次提交
  12. 03 10月, 2015 1 次提交
  13. 02 10月, 2015 1 次提交
  14. 01 10月, 2015 1 次提交
  15. 29 9月, 2015 6 次提交
  16. 25 9月, 2015 2 次提交
  17. 23 9月, 2015 3 次提交
  18. 19 9月, 2015 1 次提交
  19. 18 9月, 2015 1 次提交
  20. 16 9月, 2015 1 次提交
  21. 11 9月, 2015 1 次提交
  22. 09 9月, 2015 1 次提交
  23. 03 9月, 2015 1 次提交
  24. 02 9月, 2015 1 次提交
  25. 26 8月, 2015 1 次提交
  26. 19 8月, 2015 1 次提交
  27. 11 8月, 2015 2 次提交
  28. 03 8月, 2015 1 次提交
  29. 30 7月, 2015 1 次提交