#31774: validate_unique in Model class doesn't validate uniqueness for ImageField. -------------------------------------+------------------------------------- Reporter: Gaurav Ghildyal | Owner: nobody Type: New feature | Status: closed Component: Database layer | Version: 3.0 (models, ORM) | Severity: Normal | Resolution: needsinfo 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 Carlton Gibson): Yes, you're right: the form calls down to the model, but as I was looking, I'm wondering why the field was excluded from the check? Then, if we can make sure it's included, is it triggered? (If not, is that because the `name` isn't set yet by the storage... — and so on.) It's just a place to start looking, but from the view's point-of-view I need `form.is_valid()` to return `False`. (Hopefully that makes sense.) -- Ticket URL: <https://code.djangoproject.com/ticket/31774#comment:6> 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/067.d12e280db1249c43f6c3d3269988ea8e%40djangoproject.com.