I believe that it is already possible to trigger new migrations in a third-party app by changing its AppConfig.label, for example. Please correct me if I’m wrong.
>From that perspective, it think it wouldn’t be wrong if a migration is created >after someone changes its AppConfig’s default_auto_field. The extra migrations >could be handled manually using MIGRATION_MODULES. I feel like adding such option to AppConfig would give a pretty good flexibility, but I’m not sure it dismisses the use of settings.DEFAULT_AUTO_FIELD. Specially if one desires to keep an old default behavior. -- Caio > On Apr 10, 2020, at 04:29, Nick Pope <nickpope1...@gmail.com> wrote: > > People can also choose to set this for a third-party app by subclassing the > AppConfig, but as you say, they'd then be forced to handle migrations > manually - is this even avoidable? I'm not sure how this would look for > moving to a new default though. -- 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-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/3FE8A93E-1A7F-436D-87CC-3D87A6C16801%40gmail.com.
