#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:"7fe09e6d41b35d5a9a03783650249723313d3793" 7fe09e6d]: {{{ #!CommitTicketReference repository="" revision="7fe09e6d41b35d5a9a03783650249723313d3793" [2.2.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:5> 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 django-updates+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/067.26b503ebe5732fdbf82ed4ed1a77d2a2%40djangoproject.com.