#37057: UniqueConstraint incorrectly raises ValidationError on nullable fields
in
condition
-------------------------------------+-------------------------------------
Reporter: Drews | Owner: (none)
Type: Bug | Status: closed
Component: Database layer | Version: 6.0
(models, ORM) | Resolution:
Severity: Normal | worksforme
Keywords: UniqueConstraint | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Drews):
Replying to [comment:1 Jacob Walls]:
> Thanks, but I couldn't reproduce with the provided commands, see
[https://dryorm.xterm.info/issue-37057 fiddle].
My bad, I have created the entries via the admin site. Looks like the
UniqueConstraints aren't validated with `Device.objects.create()`.
See [https://dryorm.xterm.info/uqznomsn Updated fiddle] with
`full_clean()` call.
--
Ticket URL: <https://code.djangoproject.com/ticket/37057#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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019db548898e-e8eef42f-9e6c-4925-a3cc-0e0e34e7af0a-000000%40eu-central-1.amazonses.com.
