Code

Opened 7 years ago

Closed 7 years ago

#4055 closed (fixed)

[oracle branch] Optional "tablespace" parameter on models

Reported by: bouldersprinters Owned by: adrian
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: UI/UX:

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.

Attachments (0)

Change History (2)

comment:1 Changed 7 years ago by Simon G. <dev@…>

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Triage Stage changed from Unreviewed to Accepted

comment:2 Changed 7 years ago by bouldersprinters

  • Resolution set to fixed
  • Status changed from new to closed

(In [5022]) boulder-oracle-sprint: Fixes #4055: Added "tablespace" parameter to model metadata options to support specification of tablespaces, primarily for Oracle.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.