Make migration to uuid more robust

Instead of changing the id field, remove it and recreate it as a uuid. This shouldn't be a problem, since the external API isn't dependent on ids.
vikingco · Nov 15, 2015 · da8d03a · da8d03a
1 parent 5133d68
commit da8d03a
Showing 1 changed file with 5 additions and 1 deletion.
diff --git a/...ing/migrations/0004_auto_20150915_1411.py → ...ing/migrations/0004_auto_20151115_0703.py b/...ing/migrations/0004_auto_20150915_1411.py → ...ing/migrations/0004_auto_20151115_0703.py
@@ -12,7 +12,11 @@ class Migration(migrations.Migration):
     ]
 
     operations = [
-        migrations.AlterField(
+        migrations.RemoveField(
+            model_name='nonblockinglock',
+            name='id',
+        ),
+        migrations.AddField(
             model_name='nonblockinglock',
             name='id',
             field=models.UUIDField(default=uuid.uuid4, serialize=False, editable=False, primary_key=True),