1. 06 Oct, 2016 1 commit
  2. 13 May, 2016 2 commits
  3. 12 May, 2016 1 commit
  4. 11 May, 2016 1 commit
  5. 09 Feb, 2016 1 commit
  6. 14 Jan, 2016 1 commit
    • Change broken course_modes migration to not touch the database. · 4f323443
      Changing a field name in the way that we did (updating the Python
      variable name and switching it to point to the old DB column) confuses
      Django's migration autodetector. No DB changes are actually necessary,
      but it thinks that a field has been removed and a new one added. This
      means that Django will ask users to generate the migration it thinks
      is necessary, which ended up with us dropping data. The fix is to run
      the same migration on Django's internal model of the DB state, but not
      actually touch the DB.
      Peter Fogg committed
  7. 17 Dec, 2015 1 commit
  8. 09 Dec, 2015 1 commit
  9. 30 Nov, 2015 1 commit
  10. 10 Nov, 2015 1 commit
  11. 27 Feb, 2015 1 commit
  12. 03 Feb, 2015 1 commit
  13. 01 Dec, 2014 1 commit
  14. 05 Aug, 2014 2 commits
  15. 08 Nov, 2013 1 commit
  16. 25 Sep, 2013 1 commit
  17. 21 Aug, 2013 1 commit