[Django] #29788: Support for Oracle Managed File (OMF) Tablespaces
Django
-----------------------------------------+------------------------
Reporter: Vackar Afzal | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 2.1
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------+------------------------
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:
--
Ticket URL: <https://code.djangoproject.com/ticket/29788>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
Reporter: Vackar Afzal | Owner: nobody
Type: Uncategorized | Status: new
Severity: Normal | Resolution:
Keywords: oracle, OMF | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
-------------------------------+--------------------------------------
Changes (by Vackar Afzal):
* keywords: => oracle, OMF
* component: Uncategorized => Migrations
* easy: 0 => 1
Old description:
> 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:
New description:
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"
},
}}}
--
--
Ticket URL: <https://code.djangoproject.com/ticket/29788#comment:1>
Django
Reporter: Vackar Afzal | Owner: nobody
Type: Uncategorized | Status: new
Severity: Normal | Resolution:
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
-------------------------------+--------------------------------------
Description changed by Vackar Afzal:
Old description:
> 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"
> },
> }}}
New description:
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.[https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Appendix.Oracle.CommonDBATasks.Database.html#Appendix.Oracle.CommonDBATasks.CreatingTablespacesAndDatafiles
AmazonRDS]
--
--
Ticket URL: <https://code.djangoproject.com/ticket/29788#comment:2>
Django
Reporter: Vackar Afzal | Owner: nobody
Type: Uncategorized | Status: new
Severity: Normal | Resolution:
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
-------------------------------+--------------------------------------
Comment (by Jani Tiainen):
Can you give an example case when this is an issue?
Django itself in normal operation doesn't create datafiles nor
tablespaces.
--
Ticket URL: <https://code.djangoproject.com/ticket/29788#comment:3>
Django
Reporter: Vackar Afzal | Owner: nobody
Type: Uncategorized | Status: new
Severity: Normal | Resolution:
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
-------------------------------+--------------------------------------
Comment (by Vackar Afzal):
Yes should have been clearer, yes this relates to testing, and now that
you have mentioned it, would make more sense to add the special Key to the
'TEST' key in the DB config. i.e.
{{{
"default": {
"ENGINE": "django.db.backends.oracle",
"OPTIONS": {
"threaded": True,
},
"TEST": {
"oracle_managed_files": True # <--------------- This is the new
addition: default=False
}
"NAME": "my_sid",
"USER": "my_user",
"PASSWORD": "my_pass",
"HOST": "localhost",
"PORT": "1521"
},
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29788#comment:4>
Django
-------------------------------------+-------------------------------------
Reporter: Vackar Afzal | Owner: nobody
Component: Database layer | Version: 2.1
(models, ORM) |
Severity: Normal | Resolution:
Keywords: oracle, OMF | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by Tim Graham):
* component: Migrations => Database layer (models, ORM)
* type: Uncategorized => New feature
* easy: 1 => 0
* stage: Unreviewed => Accepted
--
Ticket URL: <https://code.djangoproject.com/ticket/29788#comment:5>
Django
-------------------------------------+-------------------------------------
Type: New feature | Status: assigned
Component: Database layer | Version: 2.1
(models, ORM) |
Severity: Normal | Resolution:
Keywords: oracle, OMF | Triage Stage: Accepted
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by felixxm):
* status: new => assigned
* owner: nobody => felixxm
--
Ticket URL: <https://code.djangoproject.com/ticket/29788#comment:6>
Django
-------------------------------------+-------------------------------------
Reporter: Vackar Afzal | Owner: felixxm
Type: New feature | Status: assigned
Component: Database layer | Version: 2.1
(models, ORM) |
Severity: Normal | Resolution:
Keywords: oracle, OMF | Triage Stage: Accepted
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by felixxm):
* has_patch: 0 => 1
Comment:
[https://github.com/django/django/pull/10617 PR]
--
Ticket URL: <https://code.djangoproject.com/ticket/29788#comment:7>
Django
-------------------------------------+-------------------------------------
Reporter: Vackar Afzal | Owner: felixxm
Component: Database layer | Version: 2.1
(models, ORM) |
Keywords: oracle, OMF | Triage Stage: Accepted
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"ff8020ed49571b0fece67d10d7398d5f57cbaa74" ff8020e]:
{{{
#!CommitTicketReference repository=""
revision="ff8020ed49571b0fece67d10d7398d5f57cbaa74"
Fixed #29788 -- Added support for Oracle Managed File (OMF) tablespaces.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29788#comment:8>