Changes between Version 8 and Version 9 of ContribAuthImprovements


Ignore:
Timestamp:
03/22/2012 09:21:10 PM (3 years ago)
Author:
russellm
Comment:

More corrections to claims for Solution 2a

Legend:

Unmodified
Added
Removed
Modified
  • ContribAuthImprovements

    v8 v9  
    117117
    118118 * Allows any user model, potentially independent of contrib.auth entirely.
    119  * Existing projects require no migration
    120  * Apps can explicitly signal their support of this new setting by using it and not referring to django.contrib.auth.User. For example, foreign key fields can be specified as `models.ForeignKey(settings.USER_MODEL)`.
     119 * Existing projects require no migration if USER_MODEL isn't modified.
    121120 
    122121Optionally:
     
    132131 * Doesn't address the !EmailField length problem for existing users. We could address this by having a User model (reflecting current field lengths) and a new !SimpleUser (that reflects better defaults); then use global_settings and project template settings to define which User is the default for new vs existing projects.
    133132 * Doesn't solve the analogous problem for any other project.
    134  * Existing apps need to be updated to reflect the fact that auth.User may not be the User model. Failure modes will be unpredictable, as auth.User will still exist as a table, but won't contain any User information.
     133 * Existing apps need to be updated to reflect the fact that auth.User may not be the User model. All instance of !ForeignKey(User) need to updated to !ForeignKey(settings.AUTH_USER). Failure modes will be unpredictable, as auth.User will still exist as a table, but won't contain any User information.
    135134 * Still has the settings-models circular dependency problem
    136135
Back to Top