django-migrations

How would I rerun a data migration on Django 1.8+? If relevant, my migration is numbered 0011_my_data_migration.py and is the latest migration. Alasdair Fake back to the migration before the one you want to rerun. ./manage.py migrate --fake yourapp 0010_my_previous_data_migration Then rerun the migration. ./manage.py migrate yourapp 0011_my_data_migration Then you can fake back to the most recent migration that you have run. In your case, you said that 0011 was the latest, so you can skip this stage. ./manage.py migrate --fake yourapp 0014_my_latest_data_migration Note that depending on the

Something went wrong on my migrations, I added a new datetimefield to a model then I used makemigrations and migrate. python manage.py makemigrations python manage.py migrate But after this the migrate got an "table already exists error". I supposed I could fake the migrations and start over, so I did python manage.py makemigrations --fake core Operations to perform: Apply all migrations: core Running migrations: Rendering model states... DONE Applying core.0001_initial... FAKED Applying core.0002_auto_20150525_1331... FAKED Applying core.0003_auto_20150525_1348... FAKED Applying core.0004

I'm using the contribute_to_class method but I don't know how to create the field in the database with new migrations. Nima To answer your question, with the new migration introduced in Django 1.7 , in order to add a new field to a model you can simply add that field to your model and initialize migrations with ./manage.py makemigrations and then run ./manage.py migrate and the new field will be added to your DB. To avoid dealing with errors for your existing models however, you can use the --fake : Initialize migrations for your existing models: ./manage.py makemigrations myapp Fake

The command python manage.py makemigrations fails most of time due to the forms.py , in which new models or new fields are referenced at class definition level. So I have to comment each such definitions for the migration to operate. It's a painfull task. I don't understand why the migration process import the forms.py module. I think that importing models modules should be sufficient. Is there a way to avoid those errors ? I was having this same issue and found the specific problem. When the migrate command was being called, Django's system checks made their way into my forms.py and then

I wanted to add some groups and assign permissions to them in a manually written migration but if I run it on a clean DB it creates permissions only after running all migrations. I've found this ticket: https://code.djangoproject.com/ticket/23422 but I cannot comment there (it's possible I was banned after expressing some discontent with GeoDjango docs), so I'll share an improvement over the solution there below. In django 1.10 the following code could be used: from django.contrib.auth.management import create_permissions def migrate_permissions(apps, schema_editor): for app_config in apps.get

I just upgraded my app to 1.7 (actually still trying). This is what i had in models.py: def path_and_rename(path): def wrapper(instance, filename): ext = filename.split('.')[-1] # set filename as random string filename = '{}.{}'.format(uuid4().hex, ext) # return the whole path to the file return os.path.join(path, filename) return wrapper class UserProfile(AbstractUser): #... avatar = models.ImageField(upload_to=path_and_rename("avatars/"), null=True, blank=True, default="avatars/none/default.png", height_field="image_height", width_field="image_width") When i try to makemigrations , it throws

I created a new app with some models and now I noticed that some of the models are poorly thought out. As I haven't committed the code the sensible thing would be to migrate the database to last good state and redo the migration with better models. In this case the last good state is database where the new app doesn't exist. How can I migrate back from initial migration in Django 1.7? In South one could do: python manage.py migrate <app> zero Which would clear <app> from migration history and drop all tables of <app> . How to do this with Django 1.7 migrations? ChillarAnand You can do the same