#30947: Apply data structure best practices to the django.contrib models and
docs
-------------------------------------+-------------------------------------
Reporter: Jon Dufresne | Owner: Ojas
Type: | Gupta
Cleanup/optimization | Status: assigned
Component: Documentation | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
> I see your point, but AFAIU, a side effect of unique_together is
creating composite database indexes, where the order of columns matters.
The order of columns within an index or unique constraints matter, but the
order of constraints doesn't. This obviously means that you can't use the
''flattened'' syntax `index_together = {'foo', 'bar'}` but favor
`index_together = {('foo', 'bar')}`.
--
Ticket URL: <https://code.djangoproject.com/ticket/30947#comment:20>
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/01070182c60e6a3e-15c3ab90-5418-4ad2-b857-ae63d402e04e-000000%40eu-central-1.amazonses.com.
