Migration Issues when updating model's default primary key from id to uuid

[Liuyang Wan]

Let's say in my Django project I have two models A and B.

class A(models.Model):

    something...

class B(models.Model):

    a = models.ForeignKey(A)

Later on I decided to use uuid as the primary key value. so I update the models:

import uuid

class A(models.Model):

     id = models.UUIDField(

         db_index=True,

         default=uuid.uuid4,

         editable=False

    )

class B(models.Model):

     id = models.UUIDField(

         db_index=True,

         default=uuid.uuid4,

         editable=False

    )

    a = models.ForeignKey(A)

Now if I make a migration, Django will NOT pick the changes with the foreign key, i.e the type of fk B.a needs to be updated to uuid as well, not integer anymore.

Is this a bug with current version of Django? What is the best practice for handling such case?

Thanks,

Liuyang

[m1chael]

i would never try to fight my database and django like that. I would add a separate uuid field

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/a68ab6ce-a1c1-42a8-b3d8-82a30edb1079%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Liuyang Wan]

Okay, user preference aside. Is this something Django couldn't handle at the moment? If so, it should be submitted as a bug.

To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.

[Tim Graham]

It's a known issue: https://code.djangoproject.com/ticket/25012.

[Liuyang Wan]

Thanks for the link. It’s interesting that two years past the bug is still unresolved.

[Thomas Leo]

I'm running django 1.11, have this same issue. Has this issue been fixed in later versions of django? Is there a workaround for 1.11?