#30903: Creating an index with specified ordering and opclass results in syntax
error.
-------------------------------------+-------------------------------------
Reporter: Hannes Ljungberg | Owner: Hannes
| Ljungberg
Type: Bug | Status: closed
Component: Database layer | Version: 2.2
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: db-indexes | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"318d186d7ed443d4c09745c755d4d186f9ed86d5" 318d186d]:
{{{
#!CommitTicketReference repository=""
revision="318d186d7ed443d4c09745c755d4d186f9ed86d5"
[3.0.x] Fixed #30903 -- Fixed migrations crash on PostgreSQL when adding
Index with opclasses and ordering.
Backport of fa5f3291e7f2611d53e64ab481ebe951b0161791 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30903#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 on the web visit
https://groups.google.com/d/msgid/django-updates/067.6f02a31859da66e471860ef194637154%40djangoproject.com.
