Add migrations due to field default changes from #10802.
Django 1.8 is more sensitive to model changes, and wants to create migrations in situations that Django 1.4 would not. Changing field defaults is an example of these situations.
Showing
- common/djangoapps/student/migrations/0002_auto_20151208_1034.py 24 additions, 0 deletions.../djangoapps/student/migrations/0002_auto_20151208_1034.py
- lms/djangoapps/shoppingcart/migrations/0002_auto_20151208_1034.py 24 additions, 0 deletions...goapps/shoppingcart/migrations/0002_auto_20151208_1034.py
Please register or sign in to comment