Converting from AutoField to BigAutoField

[Pankaj Jangid]

I have an application from 3.1.x and in 3.2 we have to explicitly state
this to make it compatible i.e. without any warning:

DEFAULT_AUTO_FIELD = 'django.db.models.AutoField'

Now suppose I want to change this to BigAutoField. What all changes I’ll
have to make in the application. Or do I just need to run migration?

--
Regards,
Pankaj Jangid

[Mike Dewhirst]

Just makemigrations and migrate.

M


--
Signed email is an absolute defence against phishing. This email has
been signed with my private key. If you import my public key you can
automatically decrypt my signature and be sure it came from me. Just
ask and I'll send it to you. Your email software can handle signing.

[Mike Dewhirst]

On 18/05/2021 3:18 pm, Mike Dewhirst wrote:
> On 18/05/2021 3:14 pm, Pankaj Jangid wrote:
>> I have an application from 3.1.x and in 3.2 we have to explicitly state
>> this to make it compatible i.e. without any warning:
>>
>> DEFAULT_AUTO_FIELD = 'django.db.models.AutoField'
>>
>> Now suppose I want to change this to BigAutoField. What all changes I’ll
>> have to make in the application. Or do I just need to run migration?
>

Should have said make the change in settings first ...

DEFAULT_AUTO_FIELD = 'django.db.models.BigAutoField'

[Pankaj Jangid]

Mike Dewhirst <mi...@dewhirst.com.au> writes:

> On 18/05/2021 3:18 pm, Mike Dewhirst wrote:
>> On 18/05/2021 3:14 pm, Pankaj Jangid wrote:
>>> I have an application from 3.1.x and in 3.2 we have to explicitly state
>>> this to make it compatible i.e. without any warning:
>>>
>>> DEFAULT_AUTO_FIELD = 'django.db.models.AutoField'
>>>
>>> Now suppose I want to change this to BigAutoField. What all changes I’ll
>>> have to make in the application. Or do I just need to run migration?
>>
>
> Should have said make the change in settings first ...
>
> DEFAULT_AUTO_FIELD = 'django.db.models.BigAutoField'
>
>> Just makemigrations and migrate.

Thanks Mike.

Regards ~Pankaj