#34949: Fails to create unique constraints
-------------------------------------+-------------------------------------
Reporter: Roman Odaisky | Owner: Jordan
| Bae
Type: Bug | Status: assigned
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Roman Odaisky):
>I'm not really sure what do we want to achieve in this ticket.
Suppose I want to write a reusable Django app that others will include in
their projects. A model in the app wants an index that’s best described as
`UniqueConstraint(fields=["a", "b"], include=["c", "d"])`. How do I make
Django create constraints and/or indexes that best approximate this on
whatever DB the user will run their project?
--
Ticket URL: <https://code.djangoproject.com/ticket/34949#comment:12>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/0107018cef2fcdad-774e1e4b-9805-4a77-a660-330a219d4616-000000%40eu-central-1.amazonses.com.
