Add support for Oracle Managed File (OMF) Tablespaces

[Vackar Afzal]

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

[Jani Tiainen]

Can you give an example case when this is an issue?

Django itself in normal operation doesn't create datafiles nor tablespaces.

[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"
    },

[Mariusz Felisiak]

​PR

[Tim Graham <timograham@…>]

In ff8020e:

Fixed #29788 -- Added support for Oracle Managed File (OMF) tablespaces.