Changes between Version 15 and Version 16 of ContribAuthImprovements

Timestamp:

Apr 3, 2012, 9:50:17 AM (13 years ago)

Author:

Alex Ogier

Comment:

Update solution 2a: auth.User doesn't need to be an orphan table causing subtle failures

ContribAuthImprovements

@@ -116 +116 @@
 Introduce an `USER_MODEL` setting (not necessarily related to `AUTH` at all) that defaults to `"auth.User"`. 
 
+Then, suppress the auth.User model when it is not in use to make failure modes predictable and noisy.
+
 There is a branch of django trunk that implements the basic idea:
 
@@ -138 +140 @@
  * 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. 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.
+ * 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).
  * Still has the settings-models circular dependency problem
  * As with Solution 2, prone to unpredictable problems if `USER_MODEL` is modified after the initial syncdb.