django-migrations

I'm running Django 1.6.6 on production and have recently upgraded to 1.9.7 on staging (dev server). This update was performed on the server and I followed the steps outlined here Upgrading from South . I noticed that the structure of the migration files have changed, and they no longer include a create statement. This causes issues because if I pull this new code from my GitHub repo and run python manage.py makemigrations or python manage.py migrate , it says: django.db.utils.OperationalError: no such table: appname_modelname The traceback points to my urls.py because I'm referencing the model

In Django, since version 1.11 we have a class for PostgreSQL GinIndex ( https://docs.djangoproject.com/en/1.11/ref/contrib/postgres/indexes/ ). I'd like to create a migration that constructs such index on a VectorSearchField I added to one of my tables. So far, I've tried to simply add db_index=True to the VectorSearchField , but that fails, because it tries to create a B-Tree index (I think) and the VectorSearchField values are too long. I managed to create the index I want by running a migrations.RunSQL() migration with: CREATE INDEX entryline_sv_index ON entryline USING GIN (sv); However, I

I'm doing some kind of refactoring for my project, where I'm relying on the django django.contrib.auth.models.Permission model. So far I define the permissions for each new user using a post_save signal, so when the user is created, I assign their permissions using user.user_permissions.add(the_permission) , this works perfectly. Now I want to use the django.contrib.auth.models.Group model to clasify the permissions a user should have. This is my code: from django.apps import AppConfig from django.db.models.signals import post_migrate from django.contrib.auth.models import Group, Permission

What is the difference between --fake-initial and --fake in Django migrations? What are the dangers of using fake migrations? Anybody knows? Thank you very much to all. I am using django 1.10 e4c5 Well the documentation is very clear about this --fake-initial Allows Django to skip an app’s initial migration if all database tables with the names of all models created by all CreateModel operations in that migration already exist. This option is intended for use when first running migrations against a database that preexisted the use of migrations. This option does not, however, check for

I have a uuid field (not a primary key). The generated migration is: from __future__ import unicode_literals from django.db import migrations, models import uuid class Migration(migrations.Migration): dependencies = [ .... ] operations = [ ... migrations.AddField( model_name='device', name='uuid', field=models.UUIDField(default=uuid.uuid4, unique=True), ), ... ] But when doing python manage.py migrate it is crashing with: django.db.utils.IntegrityError: could not create unique index "restaurants_device_uuid_key" DETAIL: Key (uuid)=(f3858ded-b8e0-4ac0-8436-8a61b10efc73) is duplicated. Strangely

I added a new, non-nullable field to my Django model and am trying to use migrations to deploy that change. How would I set default value to use for existing models to be some function of those models rather than a constant? As an example let's say I previously had a created_on field and I just added an updated_on field whose value I want to set initially to the model's created_on . How would I do this in a migration? This is what I am trying to start with: migrations.AddField( model_name='series', name='updated_as', field=models.DateTimeField(default=????, auto_now=True), preserve_default

I'm creating a data migration using the RunPython method. However when I try to run a method on the object none are defined. Is it possible to call a method defined on a model using RunPython ? chhantyal Model methods are not available in migrations, including data migrations. However there is workaround, which should be quite similar to calling model methods. You can define functions inside migrations that mimic those model methods you want to use. If you had this method: class Order(models.Model): ''' order model def goes here ''' def get_foo_as_bar(self): new_attr = 'bar: %s' % self.foo