#29549: ModelForms doesn't validate CHOICES -------------------------------------+------------------------------------- Reporter: Evgeny Arshinov | Owner: nobody Type: Uncategorized | Status: new Component: Database layer | Version: 1.11 (models, ORM) | Severity: Normal | Resolution: Keywords: | Triage Stage: | Unreviewed Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+-------------------------------------
Comment (by Tim Graham): Did you mean to title the ticket "Model.save() doesn't validate CHOICES"? This is [https://docs.djangoproject.com/en/dev/ref/models/instances/#django.db.models.Model.clean documented]: > Note, however, that like Model.full_clean(), a model’s clean() method is not invoked when you call your model’s save() method. This is because of backwards compatibility (and probably performance considerations). There are ways to [https://stackoverflow.com/questions/4441539/why-doesnt- djangos-model-save-call-full-cleanchange change the behavior in your project]. -- Ticket URL: <https://code.djangoproject.com/ticket/29549#comment:1> 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/067.2897f8f751247c38fa6607431792b233%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.