#20888: Allow defining order of column for indexes
-------------------------------------+-------------------------------------
Reporter: anonymous | Owner: Akshesh
| Doshi
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: index, order, db- | Triage Stage: Accepted
indexes 1.11 |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* keywords: index, order, db-indexes => index, order, db-indexes 1.11
* status: closed => new
* has_patch: 1 => 0
* resolution: fixed =>
Comment:
We need to revisit this as on PostgreSQL 9.6, "column am.amcanorder does
not exist".
According to a post on the PostgreSQL mailing list: "Using
`pg_get_indexdef()` would leave you much less vulnerable to cross- version
differences in the system catalogs.
--
Ticket URL: <https://code.djangoproject.com/ticket/20888#comment:16>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.63d81e180bae9fb35cd1abc32cf37267%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
