Opened 18 years ago
Closed 18 years ago
#4055 closed (fixed)
[oracle branch] Optional "tablespace" parameter on models
| Reported by: | Matt Boersma | Owned by: | Adrian Holovaty |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | other branch |
| Severity: | Keywords: | oracle tablespace | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
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.
Having a "tablespace" parameter, probably attached to the Meta inner class, would help a lot. Most backends can just ignore it, but Oracle can add "TABLESPACE [name]" to the end of each TABLE CREATE stanza. And there will be rejoicing.
Change History (2)
comment:1 by , 18 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:2 by , 18 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
(In [5022]) boulder-oracle-sprint: Fixes #4055: Added "tablespace" parameter to model metadata options to support specification of tablespaces, primarily for Oracle.