1. 30 Aug, 2016 1 commit
  2. 03 Aug, 2016 1 commit
  3. 09 May, 2016 1 commit
  4. 02 May, 2016 2 commits
  5. 12 Apr, 2016 2 commits
  6. 08 Apr, 2016 1 commit
  7. 07 Mar, 2016 1 commit
  8. 29 Feb, 2016 1 commit
    • Create a new CSMHExtended table to hold our new data · dd90c556
      This is a clone (copy) of CSMH's declaration and methods with an added
      id of UnsignedBigInAutoField
      
      We should be able to delete the save_history code, but needs testing.
      
      Add error logging when capa failures happen
      
      Put StudentModuleHistory into its own database
      
      Bump out the primary key on CSMHE
      
      This gives us a gap to backfill as needed.
      Since the new table's pk is an unsigned bigint, even for people who don't
      consolidate CSMH into CSMHE, the lost rows are unlikely to matter.
      
      Remove StudentModuleHistory cleaner
      Calen Pennington committed
  9. 11 Dec, 2015 2 commits
  10. 10 Nov, 2015 1 commit
  11. 27 Aug, 2015 1 commit
  12. 02 Jul, 2015 1 commit
  13. 07 May, 2015 1 commit
  14. 02 Apr, 2015 1 commit
  15. 30 Mar, 2015 1 commit
  16. 10 Mar, 2015 1 commit
  17. 09 Feb, 2015 4 commits
  18. 04 Feb, 2015 2 commits
    • Better support specifying of modulestore configuration in test cases · b353ed2e
      The existing pattern of using `override_settings(MODULESTORE=...)` prevented
      us from having more than one layer of subclassing in modulestore tests.
      
      In a structure like:
      
          @override_settings(MODULESTORE=store_a)
          class BaseTestCase(ModuleStoreTestCase):
              def setUp(self):
                  # use store
      
          @override_settings(MODULESTORE=store_b)
          class ChildTestCase(BaseTestCase):
              def setUp(self):
                  # use store
      
      In this case, the store actions performed in `BaseTestCase` on behalf of
      `ChildTestCase` would still use `store_a`, even though the `ChildTestCase`
      had specified to use `store_b`. This is because the `override_settings`
      decorator would be the innermost wrapper around the `BaseTestCase.setUp` method,
      no matter what `ChildTestCase` does.
      
      To remedy this, we move the call to `override_settings` into the
      `ModuleStoreTestCase.setUp` method, and use a cleanup to remove the override.
      Subclasses can just defined the `MODULESTORE` class attribute to specify which
      modulestore to use _for the entire `setUp` chain_.
      
      [PLAT-419]
      Calen Pennington committed
  19. 02 Dec, 2014 2 commits
  20. 31 Oct, 2014 1 commit
  21. 22 Oct, 2014 1 commit
  22. 22 Sep, 2014 1 commit
  23. 10 Jul, 2014 1 commit
  24. 26 Jun, 2014 1 commit
  25. 29 May, 2014 1 commit
  26. 06 May, 2014 1 commit
    • Make course ids and usage ids opaque to LMS and Studio [partial commit] · 9811926d
      This commit updates lms/djangoapps/courseware.
      
      These keys are now objects with a limited interface, and the particular
      internal representation is managed by the data storage layer (the
      modulestore).
      
      For the LMS, there should be no outward-facing changes to the system.
      The keys are, for now, a change to internal representation only. For
      Studio, the new serialized form of the keys is used in urls, to allow
      for further migration in the future.
      
      Co-Author: Andy Armstrong <andya@edx.org>
      Co-Author: Christina Roberts <christina@edx.org>
      Co-Author: David Baumgold <db@edx.org>
      Co-Author: Diana Huang <dkh@edx.org>
      Co-Author: Don Mitchell <dmitchell@edx.org>
      Co-Author: Julia Hansbrough <julia@edx.org>
      Co-Author: Nimisha Asthagiri <nasthagiri@edx.org>
      Co-Author: Sarina Canelake <sarina@edx.org>
      
      [LMS-2370]
      Calen Pennington committed
  27. 14 Mar, 2014 1 commit
  28. 12 Mar, 2014 1 commit
  29. 07 Mar, 2014 1 commit
  30. 03 Jan, 2014 1 commit