#36808: Make UniqueConstraint name required in signature
-------------------------------------+-------------------------------------
Reporter: Jonathan Biemond | Owner: Jonathan
Type: | Biemond
Cleanup/optimization | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls <jacobtylerwalls@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"b172cbdf33c3eaea6a5c4a53da2ed0e46306a625" b172cbd]:
{{{#!CommitTicketReference repository=""
revision="b172cbdf33c3eaea6a5c4a53da2ed0e46306a625"
Fixed #36808 -- Required name argument in UniqueConstraint signature.
By trading ValueError for TypeError for omitted name arguments,
we gain a little clarity.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36808#comment:4>
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/0107019b371544bd-e938a1c6-693f-4142-b3e8-805ad0fcb540-000000%40eu-central-1.amazonses.com.
