On Tue, Mar 20, 2012 at 5:17 PM, Alex Ogier <alex.og...@gmail.com> wrote: >> Would something like the following alleviate that problem? >> >> class User(models.Model): >> if settings.USE_LONG_USER_FIELDS: >> username = models.CharField(max_length=255, unique=True, ...) >> else: >> username = models.CharField(max_length=30, unique=True, ...) >> ... > > Maybe, but there's a lot more than username length that people want to > change. Adding piecemeal settings to manage all this is putting wallpaper > over gaping holes. It's not a good long-term solution. >
There is a long list of new features people would like to have with auth Models. All I would like is that as well as these wonderful new features, we also pay some attention to fixing bugs. Am I the only person who thinks it is strange to completely re-do auth and NOT fix the underlying problems? You can add the same settings to whatever long term solution is deemed appropriate, as the current plan for that is to have the stock pluggable User model have the same length fields as the existing one. Adding piecemeal settings is not good, however this solution does solve the email and username length issues for: * Users who read relnotes and want to fix their models * Users who make new projects It also doesn't affect: * Users who don't read relnotes * Users who read relnotes but don't want to fix their models None of the other proposed solutions immediately fix the default username and email length issues for new projects. 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.
