64 bits is the default for new projects. See the 3.2 release notes: https://docs.djangoproject.com/en/dev/releases/3.2/
On Fri, 29 Jan 2021 at 17:23, Christophe Pettus <x...@thebuild.com> wrote: > > > > On Jan 29, 2021, at 07:40, charettes <charett...@gmail.com> wrote: > > > > As Tom said Django 3.2 supports swapping the default primary key of > models so the integer exhaustion part of your suggestion should be addressed > > That's not particularly related. The issue isn't that there isn't any way > to get a 64 bit key; there is, of course, using AutoBigField. It's that > the default, based on all of the documentation and code samples available, > is to get a 32 bit key using AutoField, and that's a foot-gun with a > long-delayed firing time. > > The essence of the proposal is to make the public default for new projects > 64 bit keys; we're doing developers a disservice by making the default path > 32 bit keys. > > -- > -- Christophe Pettus > x...@thebuild.com > > -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/C0092F9E-71ED-463D-A0A8-4F00D8F00889%40thebuild.com > . > -- Adam -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMyDDM2t7PO20ARuJoVh5ZijzNWwicK_YwQOuKk6Ov0nW4yG%2Bg%40mail.gmail.com.
