1. 01 Apr, 2016 1 commit
  2. 01 Feb, 2016 1 commit
    • Remove uses of using() from migrations · 2d9708da
      This hardcoded the db_alias fetched from schema_editor and forces django
      to try and migrate any second database you use, rather than routing to
      the default database.  In testing a build from scratch, these do not
      appear needed.
      
      Using using() prevents us from using multiple databases behind edxapp.
      
      Additionally - add back a removed backwards migration from certificates
      0003.  I have no idea why this was dropped in the 1.8 upgrade.
      Kevin Falcone committed
  3. 11 Nov, 2015 1 commit
    • More-correct data migrations · e7fcc743
      We need to be sure the migrations will work even in the presence of data
      from the future.  get_or_create is a problem, because if the data
      already exists, there could be more than one record, even if this
      migration only creates one.
      Ned Batchelder committed
  4. 10 Nov, 2015 1 commit