1. 30 May, 2016 1 commit
  2. 13 May, 2016 1 commit
  3. 03 May, 2016 1 commit
  4. 14 Apr, 2016 3 commits
  5. 10 Apr, 2016 1 commit
  6. 20 Mar, 2016 1 commit
  7. 19 Mar, 2016 1 commit
  8. 11 Mar, 2016 2 commits
  9. 10 Mar, 2016 2 commits
  10. 09 Mar, 2016 1 commit
  11. 19 Feb, 2016 1 commit
  12. 15 Feb, 2016 2 commits
  13. 04 Feb, 2016 2 commits
  14. 03 Feb, 2016 1 commit
  15. 23 Jan, 2016 1 commit
  16. 22 Jan, 2016 1 commit
  17. 21 Jan, 2016 2 commits
  18. 20 Jan, 2016 2 commits
  19. 13 Jan, 2016 1 commit
  20. 08 Jan, 2016 1 commit
  21. 07 Jan, 2016 1 commit
    • Yorick Peterse's avatar
      Sort by ID when sorting using "Recently created" · 9dacc3bc
      Yorick Peterse authored
      Sorting by "id" has the same effect as sorting by created_at while
      performing far better and without the need of an extra index (in case
      one wanted to speed up sorting by "created_at").
      
      Sorting by "Recently updated" still uses the physical "updated_at"
      column as there's no way to use the "id" column for this instead.
      9dacc3bc
  22. 24 Dec, 2015 4 commits
  23. 15 Dec, 2015 1 commit
  24. 17 Nov, 2015 1 commit
  25. 02 Nov, 2015 1 commit
  26. 21 Oct, 2015 1 commit
  27. 20 Oct, 2015 3 commits