On Fri, Jan 24, 2014 at 9:05 AM, Brian Neal <[email protected]> wrote:
> Hello, > > The deprecation timeline says this about Django 1.7: > > "The AUTH_PROFILE_MODULE setting, and the get_profile() method on the > User model, will be removed." > > The dev 1.7 release notes say that the new schema migration is scheduled > to land in 1.7. > > Does this mean we cannot use the new schema migration functionality to > migrate away from AUTH_PROFILE_MODULE? Would it be better to deprecate the > AUTH_PROFILE_MODULE in 1.8? That way the features could co-exist together > for a brief time in order to facilitate migration. > > Hi Brian, There's a problem with your proposal - what profile are you suggesting that we migrate *to*? Migrations are only helpful if you've got a plan for how the data is changing. We've removed AUTH_PROFILE_MODULE because there's a number of ways that this data could be stored: * On a custom User model * On a related model linked with a FK * On a related model linked with a O2O relation * On a separate model indexed by user ID There's no migration path for simply *removing* AUTH_PROFILE_MODULE either. The database table for User never had a formal representation of AUTH_PROFILE_MODULE - it was just a O2O relation that had a specialised caching implementation. When AUTH_PROFILE_MODULE disappears, you'll still be able to access profile modules - the name will just change. So - there might be a role for migrations to play, but it's not something Django can specify as a project -- you'll have to handle it on a per-project basis. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJxq8480KafZ-Ocq%2B%3DmFW2-ERymAkc_rPrS2S1TKNz3NO7kDqg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
