#22374: Suggest to validate unique before running clean in models full_clean
etc..
----------------------------------------------+--------------------
Reporter: dspjmt@… | Owner: nobody
Type: Bug | Status: new
Component: Database layer (models, ORM) | Version: 1.6
Severity: Release blocker | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------------------+--------------------
If we use clean(), and check for fields the hasn't been assigned, then it
will raise a doesnotexist exception.
The clean() method claims we can utilize fields which data is clean, it's
not, will in validation of uniqueness, the missing of fields will be
suggested successfully, I think we should check if the field exists first.
--
Ticket URL: <https://code.djangoproject.com/ticket/22374>
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/059.56af3b723e520ccc16c13437c204d5b1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
