#12900: EmailField max_length of 75 characters should be 256 acccording to RFC 5321 -------------------------------------+------------------------------------- Reporter: | Owner: nobody artem.skvira@… | Status: closed Type: | Component: Database layer Uncategorized | (models, ORM) Milestone: | Severity: Normal Version: 1.1 | Keywords: Resolution: duplicate | Has patch: 0 Triage Stage: | Needs tests: 0 Unreviewed | Easy pickings: 0 Needs documentation: 0 | Patch needs improvement: 0 | -------------------------------------+------------------------------------- Changes (by TomaszZielinski):
* cc: tomasz.zielinski@… (added) * type: => Uncategorized * severity: => Normal * easy: => 0 Comment: JFYI I was successfull with monkey-patching of auth.User model with: User._meta.get_field_by_name('email')[0].max_length = 256 There was "only" one problem with this - when I put it into models.py which also contained my custom UserProfile model, then depending on the position (in source file) of the monkey patch line relative to UserProfile model, the backreference from UserProfile to User was - or was not created. Other than that, everything has so far worked like a charm, including South migrations. -- Ticket URL: <http://code.djangoproject.com/ticket/12900#comment:2> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To post to this group, send email to django-updates@googlegroups.com. To unsubscribe from this group, send email to django-updates+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-updates?hl=en.