Re: DEFAULT_AUTO_FIELD

As Mariusz wrote, it depends upon at least the M2M field migration being fixed first. ‪On Mon, 4 Oct 2021 at 10:36, ‫אורי‬‎ wrote:‬ > Thank you. > > >> In a future Django release the default value of DEFAULT_AUTO_FIELD >>>

Re: DEFAULT_AUTO_FIELD

Hi, As far as I know this is why BigAutoField is for. I guess the AutoField is there for backwards compatibility. -- Pavlos Georgiadis On 4/10/21 11:58, אורי wrote: Hi, Are there any intentions to make DEFAULT_AUTO_FIELD and django.db.models.AutoField a 64-bit integers in future versions

Re: DEFAULT_AUTO_FIELD

Thank you. > In a future Django release the default value of DEFAULT_AUTO_FIELD >> >> will be changed to BigAutoField >> >>

Re: DEFAULT_AUTO_FIELD

The startproject template already uses 64 bit integers, and the default will change in a future version. See the 3.2 release notes ( https://docs.djangoproject.com/en/3.2/releases/3.2/#customizing-type-of-auto-created-primary-keys ) : Starting with 3.2 new projects are generated with DEFAULT_AUTO_

Re: DEFAULT_AUTO_FIELD

Hi, *Are there any intentions to make ... django.db.models.AutoField a 64-bit > integers in future versions of Django?* > `AutoField` is a completely valid field, I don't see a reason to remove it or make it an alias of the `BigAutoField`. > Are there any intentions to make *DEFAULT_AUTO_FI