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?
On Sunday, November 12, 2017 at 7:30:45 AM UTC-5, Liuyang Wan wrote:
>
> Thanks for the link. It’s interesting that two years past the bug is still
> unresolved.
Thanks for the link. It’s interesting that two years past the bug is still
unresolved.
--
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+unsubscr...@
Okay, user preference aside. Is this something Django couldn't handle at
the moment? If so, it should be submitted as a bug.
On Saturday, November 11, 2017 at 10:22:03 PM UTC+8, mike wrote:
>
> i would never try to fight my database and django like that. I would add a
> separate uuid field
>
>
i would never try to fight my database and django like that. I would add a
separate uuid field
On Fri, Nov 10, 2017 at 10:54 PM, Liuyang Wan wrote:
> Let's say in my Django project I have two models A and B.
>
> class A(models.Model):
> something...
>
> class B(models.Model):
> a = model
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(
5 matches
Mail list logo
