Changes between Version 11 and Version 12 of ContribAuthImprovements

Timestamp:

Mar 23, 2012, 6:21:09 AM (14 years ago)

Author:

bhuztez

Comment:

add solution 2b AUTH_USER_MODEL_MIXINS setting

ContribAuthImprovements

@@ -138 +138 @@
  * As with Solution 2, prone to unpredictable problems if `USER_MODEL` is modified after the initial syncdb.
 
+== Solution 2b: `AUTH_USER_MODEL_MIXINS` setting ==
+
+This is similar to solution 2 and 2a, but is quite the opposite to solution 3.
+
+Making every model pluggable. So that auth.User could be defined like this.
+
+{{{#!python
+class User(models.Model):
+    __mixins__ = settings.AUTH_USER_MODEL_MIXINS
+}}}
+
+=== Implementation ===
+
+ * Change bases before creating user-defined Model class in !ModelBase.
+     {{{#!python
+     mixins = attrs.get('__mixins__', ())
+     bases = load_available_model_mixins(mixins) + bases
+     }}}
+ * separate fields out as mixins like solution 2a
+
+=== Advantages ===
+
+ * do not have unpredictable problems in solution 2/2a.
+ * Existing projects require no migration. the same as solution 2/2a.
+ * Unlike solution 2a, change is not required for existing apps. 
+ * Unrelated and third-party apps can indicate that they depend on various orthogonal mixins. the same as solution 2.
+
+=== Problems ===
+
+ * built-in schema migration tools is required.
+ * Doesn't address the !EmailField length problem. (can be solved by schema migration tools?)
+ * !ModelForm must be more restrictive, otherwise, django will suffer security issues, just as the register_globals of PHP or the mass-assignment of Rails.
+
 == Solution 3: Leverage App Refactor ==