Opened 12 years ago

Closed 12 years ago

#4056 closed (fixed)

[oracle branch] Optional "tablespace" parameter for indexes

Reported by: Matt Boersma Owned by: Adrian Holovaty
Component: Database layer (models, ORM) Version: other branch
Severity: Keywords: oracle tablespace
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


You won't find a real Oracle schema in the wild that doesn't use multiple TABLESPACES to organize data storage. While Django's ORM will never emit production DDL that a DBA accepts without modifications, we can try.

A very common performance-oriented paradigm in Oracle is to store database indexes in their own tablespace. If Django columns accepted an optional "tablespace" parameter in combination with "index=True," the Oracle backend could create the proper DDL for this.

Change History (1)

comment:1 Changed 12 years ago by Matt Boersma

Resolution: fixed
Status: newclosed

(In [5027]) boulder-oracle-sprint: Fixed #4056: Added optional "tablespace" parameter to Fields to specify a tablespace for the column's index in backends that support it, primarily for use in Oracle.

Note: See TracTickets for help on using tickets.
Back to Top