I agree that it will be complicated, hard, and time consuming problem to solve but I would like to explore what it would take to attempt and if it would even be possible.
We could start with standard PK substitutes such as UUID's and then expand from there as needed. On Tuesday, August 30, 2016 at 11:43:17 AM UTC-7, Tim Graham wrote: > > Sounds quite complicated. In particular, how could we reasonably test that > contrib apps work with arbitrary PKs? > > On Tuesday, August 30, 2016 at 2:32:18 PM UTC-4, Emett Speer wrote: >> >> Hello Everyone, >> >> I would like to propose the exploration of adding a default PK setting do >> Django. This could be a flag at project creation time or a setting to be >> set before the first migration takes place. >> >> This would allow the developer to set the default PK in Django to >> something like UUID. With this things like the default Group, User, etc.. >> models would have UUID based PK's rather then Int based ones and all future >> tables would have UUID PK's by default. >> >> Please let me know what you think. >> > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/ef0778b4-2190-415e-a2c5-739a123fc114%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
