> There are plenty of other workarounds -- the easiest is to note the > email field is optional and just create a RealUserEmail object with a > OneToOne to User. Given that, a hacky workaround in Django itself just > isn't going to happen. The right thing to do is to get the auth > refactor done and solve this and all the other issues at the same > time.
Might one of those "other issues" be schema migration? As the contrib apps mature, it seems that these types of problems will recur with greater frequency up until the point that South-like migrations become something that contrib apps can use. I would hate to think that every minor bug or feature enhancement such as this that affects database tables can only be fixed by a comprehensive rewrite of the subsystem :) I guess my substantive questions are these: Will the timeline of Jan Rzepecki's GSoC project permit the inclusion of "schema alteration" into Django 1.4? and: Is the "schema alteration" API that is envisioned by that project going to be full-featured enough to allow for migrations to be added to contrib apps that interact with the database? Regards, Eduardo -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
