#27098: Deprecate DatabaseIntrospection.get_indexes
-------------------------------------+-------------------------------------
Reporter: claudep | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database | Version: master
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
`DatabaseIntrospection.get_indexes` outputs a subset of
`DatabaseIntrospection.get_constraints`, however only for single-column
indexes. The use case was mainly for `inspectdb` primary key and unique
detections, and for some tests. Now that multicolumn indexes is in sight,
that API is less appealing and appears unnecessary (see also
ticket:16220#comment:19).
--
Ticket URL: <https://code.djangoproject.com/ticket/27098>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/050.fa0ada3213deec691acff979a6d4bf02%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
