#16220: Add introspection for multicolumn indexes
-------------------------------------+-------------------------------------
     Reporter:  jgelens              |                    Owner:  jgelens
         Type:                       |                   Status:  new
  Cleanup/optimization               |                  Version:  1.3
    Component:  Database layer       |               Resolution:
  (models, ORM)                      |             Triage Stage:  Design
     Severity:  Normal               |  decision needed
     Keywords:  dceu2011 inspectdb   |      Needs documentation:  0
    Has patch:  0                    |  Patch needs improvement:  0
  Needs tests:  0                    |                    UI/UX:  0
Easy pickings:  0                    |
-------------------------------------+-------------------------------------

Comment (by hvdklauw):

 I did note some inconsistencies between the different backends. (SQLite
 didn't output unique indexes)

 Now they do the same, still not sure about the key values, you can't use
 the field name as there might be multiple.

 I don't have access or knowledge of Oracle, so someone who does should fix
 that; also haven't written tests because django by itself doesn't support
 adding indexes on multiple fields (need #5805 for that, which in turn
 needs this to do tests)

-- 
Ticket URL: <https://code.djangoproject.com/ticket/16220#comment:13>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Reply via email to