DEFAULT_AUTO_FIELD

[אורי‎]

Hi,

Are there any intentions to make DEFAULT_AUTO_FIELD and django.db.models.AutoField a 64-bit integers in future versions of Django?

If not, why not?

Thanks,

אורי

u...@speedy.net

[Mariusz Felisiak]

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_FIELD ... a 64-bit integers in future versions of Django?

As far as I'm aware this will not happen in the nearest future (maybe never). I cannot imagine that we would change the default for the DEFAULT_AUTO_FIELD setting before:

• dropping support for all versions prior to 3.2 (maybe Django 5.0+), and
  
• fixing remaining issue with the smooth migration between auto-fields, e.g. #32674.
  

Best,
Mariusz

[Adam Johnson]

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_FIELD set to BigAutoField. Also, new apps are generated with AppConfig.default_auto_field set to BigAutoField. In a future Django release the default value of DEFAULT_AUTO_FIELD will be changed to BigAutoField.

--
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-develop...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CABD5YeGT-O0XMkZjC%3Dh%3DMWcJFEBo%3D%2BzXWpuBFfUsO5vJ3ZLH7g%40mail.gmail.com.

[אורי‎]

Thank you.

 

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

When do you expect this to happen?

[Pavlos Georgiadis]

Hi,

As far as I know this is why BigAutoField is for. I guess the AutoField is there for backwards compatibility.

--
Pavlos Georgiadis

[Adam Johnson]

As Mariusz wrote, it depends upon at least the M2M field migration being fixed first.

--

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-develop...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CABD5YeEPftdb_YRkbE1HK%2B%2BO34q%3DrvGr3wkuP6%3DR8Puuh%2B4sVA%40mail.gmail.com.