Opened 7 years ago
Last modified 7 years ago
#29788 closed New feature
Support for Oracle Managed File (OMF) Tablespaces — at Version 2
| Reported by: | Vackar Afzal | Owned by: | nobody | 
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | 2.1 | 
| Severity: | Normal | Keywords: | oracle, OMF | 
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no | 
| Needs tests: | no | Patch needs improvement: | no | 
| Easy pickings: | no | UI/UX: | no | 
Description (last modified by )
Oracle has 2 means of creating tablespaces:
- Oracle managed files (OMF)
- User managed files (UMF)
Currently Django only supports UMF, and not OMF.
To add support for OMF just need to omit the 'name' of the datafile - very simple changed.
Could add a flag to the 'OPTIONS' key in the database settings to specify which should be used:
    "default": {
      "ENGINE": "django.db.backends.oracle",
      "OPTIONS": {
        "threaded": True,
        "oracle_managed_files": True # <--------------- This is the new addition: default=False
      },
      "NAME": "my_sid",
      "USER": "my_user",
      "PASSWORD": "my_pass",
      "HOST": "localhost",
      "PORT": "1521"
    },
This is required if you are working with an Oracle instance that only supports OMF i.e.AmazonRDS
Change History (2)
comment:1 by , 7 years ago
| Component: | Uncategorized → Migrations | 
|---|---|
| Description: | modified (diff) | 
| Easy pickings: | set | 
| Keywords: | oracle OMF added | 
comment:2 by , 7 years ago
| Description: | modified (diff) | 
|---|
  Note:
 See   TracTickets
 for help on using tickets.