On Tue, Aug 02, 2016 at 06:09:00PM +0300, Shai Berger wrote: > Well, there's one precedent that is quite pertinent here, and that > is AUTH_USER_MODEL. But a setting for the length of a field in a > built-in app is problematic because it would imply a migration in > that app, rather than user apps. > > In principle we could write the d.c.auth migration by hand to take > the setting in account, and declare the setting as unchangeable like > AUTH_USER_MODEL, but that would be very ugly special-casing IMO.
That would be very error prone, unless we wrap in a thick layer of safety checks. django-allauth already does something like that (where a migration conditionally adds an operation depending on a setting) and it has already come up a bunch of times in #django when people got their database schema into an inconsistent state by changing that setting. -- 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 post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/20160802151714.GG5430%40koniiiik.org. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Digital signature
