On Thu, Feb 18, 2010 at 8:15 AM, Artem Skvira <[email protected]> wrote: > Hi all, > > Following the django's tracker policy I'dlike to discuss this issue > here instead of re-opening the ticket (http://code.djangoproject.com/ > ticket/12900#comment:1) > > My problem with current limitation of 75 characters is that it does > not allow me to use auth.User.email for storage of login details. > While there's certainly a workaround (using custom profile model) I am > wondering what are the potential problems with the change to auth.User > itself and why it might not be backwards compatible for existing > django applications already using this field in User?
Two examples of problems that would emerge: * Test databases wouldn't match production databases, since test databases would be created with the new field size. * Form validation behavior would change. The max_length argument on the field is used to determine the maximum allowed length for inputs; if the field definition doesn't match the database, you would be able have a form definition that marks input as valid that the database can't accept. Addressing the limitations of the builtin auth.User is something I hope to look at in the 1.3 timeframe. Yours, Russ Magee %-) -- 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.
