#32834: DEFAULT_AUTO_FIELD should allow for diable migration for existing models
------------------------------------+--------------------------------------
     Reporter:  qiu-lijie           |                    Owner:  nobody
         Type:  New feature         |                   Status:  closed
    Component:  Migrations          |                  Version:  3.2
     Severity:  Normal              |               Resolution:  invalid
     Keywords:  DEFAULT_AUTO_FIELD  |             Triage Stage:  Unreviewed
    Has patch:  0                   |      Needs documentation:  0
  Needs tests:  0                   |  Patch needs improvement:  0
Easy pickings:  0                   |                    UI/UX:  0
------------------------------------+--------------------------------------
Changes (by Mariusz Felisiak):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 > While I understand Django wants to move away AutoField and towards
 BigAutoField for pk

 First of all I would like to ensure you that this will not happen in the
 nearest future (maybe never). I can not imagine that we would change that
 before dropping support for all versions prior to 3.2.

 > the current behaviour will make migrations for third-party apps, which
 is not desirable

 3rd-party apps can set `AppConfig.default_auto_field` to the
 `'django.db.models.AutoField'` to avoid migrations, you can also set
 `DEFAULT_AUTO_FIELD = 'django.db.models.AutoField'` in your project.

 We allowed customization at all levels (project, app, model) see
 [https://docs.djangoproject.com/en/3.2/releases/3.2/#customizing-type-of-
 auto-created-primary-keys release notes]. Also it looks that
 [https://pypi.org/project/django-allauth/ django-allauth] and
 [https://pypi.org/project/django-cities-light/ django-cities-light] don't
 officially support Django > 3.2, you can try to report this in their
 bugtrackers.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/32834#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.8dce7d34c04231d9cecad1ee941703d0%40djangoproject.com.

Reply via email to