#33773: DEFAULT_INDEX_TABLESPACE setting is ignored for Indexes defined with
multiple fields.
------------------------------+------------------------------------
Reporter: Bruce Cutler | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 4.0
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+------------------------------------
Changes (by Simon Charette):
* component: Database layer (models, ORM) => Migrations
* stage: Unreviewed => Accepted
Comment:
Thank you for your report.
There's effectively a discrepancy between
[https://docs.djangoproject.com/en/4.0/topics/db/tablespaces/#declaring-
tablespaces-for-indexes what's documented] and how
[https://github.com/django/django/blob/e96320c91724830034033a9cb8afd9cf8c11e2fd/django/db/backends/base/schema.py#L1305-L1313
it's implemented for indexes including multiple fields or solely
expressions].
Would you be interested in submitting a patch that makes
`_get_index_tablespace_sql` consider `DEFAULT_INDEX_TABLESPACE` before
`model._meta.db_tablespace` if the former is defined?
--
Ticket URL: <https://code.djangoproject.com/ticket/33773#comment:1>
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/0107018148f1aac4-be97deb0-99d4-48b5-955b-382ad6b34b4c-000000%40eu-central-1.amazonses.com.
