> > It looks OK, but there is one really big issue with your approach - > database blowup. > You can easily choose mixins to compose your User model, but once it's > done your database layout is fixed. > If you then decide to use different mixins - it would be impossible > without very smart db schema migration tool. >
Any schema migration tool that reuses django's ORM *should* be OK. For example, South works just fine. Adding or removing a mixin is exactly like adding or removing the fields in that mixin as far as the ORM is concerned. If we end up patching the User model in-place, then the tool will have to be able to operate on models in contrib apps which might be in read-only locations or shared locations, but this has been on the radar of most migration tools for a while already. For example, South has the SOUTH_MIGRATION_MODULES<http://south.aeracode.org/docs/settings.html#south-migration-modules>setting to handle this. -Alex Ogier -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
