#22630: models.EmailField allows a dict to be saved without raising an error resulting in Python dict strings saved to the DB -------------------------------------+------------------------------------- Reporter: joe@… | Owner: nobody Type: Bug | Status: closed Component: Database layer | Version: 1.4 (models, ORM) | Resolution: needsinfo Severity: Normal | Triage Stage: Keywords: email orm field | Unreviewed validators | Needs documentation: 0 Has patch: 0 | Patch needs improvement: 0 Needs tests: 0 | UI/UX: 0 Easy pickings: 0 | -------------------------------------+-------------------------------------
Comment (by timo): In the example gist, you haven't actually [https://docs.djangoproject.com/en/dev/ref/models/instances/#validating- objects invoked model validation] before you saved the object. Does adding `email.full_clean()` before `save()` change anything? -- Ticket URL: <https://code.djangoproject.com/ticket/22630#comment:5> 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 unsubscribe from this group and stop receiving emails from it, send an email to django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/074.3e79ed1a18b3a2f67492b651201b8802%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.