On Sat, Feb 18, 2012 at 4:25 AM, Tai Lee <real.hu...@mrmachine.net> wrote: > It's not that hard to just set up a OneToOneField back to User, and > use signals to automatically create a User when you create your own > User/Profile. Then you can still make use of 3rd party apps that rely > on contrib.auth or contrib.sessions, and also make use of groups from > contrib.auth, etc. > > Cheers. > Tai. >
Once you are aware of the issue, it's easier to change the code so that it DTRT in the first place. Any other solution has notable downsides, like the username field not being what the user enters to log in with, the email field not being correct. Eg, with your fix authenticating/storing longer emails on a UserProfile object may work, but it's unlikely that third party code which sends emails will be aware that the correct email address to use is user.get_profile().real_email_field rather than user.email. Those sorts of bugs are much harder to find/fix than the actual bugs, which are that both email and username fields are too short, and the username field has arbitrary restrictions on what it can contain. Cheers Tom -- 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.
