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
>>> <https://docs.djangoproject.com/en/3.
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
Thank you.
> In a future Django release the default value of DEFAULT_AUTO_FIELD
>> <https://docs.djangoproject.com/en/3.2/ref/settings/#std:setting-DEFAULT_AUTO_FIELD>
>> will be changed to BigAutoField
>> <https://docs.djangoproject.com/en/3.2/ref/models/fields/
with DEFAULT_AUTO_FIELD
> <https://docs.djangoproject.com/en/3.2/ref/settings/#std:setting-DEFAULT_AUTO_FIELD>
> set to BigAutoField
> <https://docs.djangoproject.com/en/3.2/ref/models/fields/#django.db.models.BigAutoField>.
> Also, new apps are generated with AppConfig.def
s 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 prio
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
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contribu
