Changes between Version 8 and Version 9 of ContribAuthImprovements

Timestamp:

Mar 22, 2012, 9:21:10 PM (12 years ago)

Author:

Russell Keith-Magee

Comment:

More corrections to claims for Solution 2a

ContribAuthImprovements

@@ -117 +117 @@
 
  * Allows any user model, potentially independent of contrib.auth entirely.
- * Existing projects require no migration
- * 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)`.
+ * Existing projects require no migration if USER_MODEL isn't modified.
  
 Optionally:
@@ -132 +131 @@
  * 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.
  * Doesn't solve the analogous problem for any other project.
- * 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.
+ * 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.
  * Still has the settings-models circular dependency problem