#31908: Add parallel testing support to Oracle backend
-------------------------------------+-------------------------------------
Reporter: Ahmad A. Hussein | Owner: (none)
Type: New feature | Status: new
Component: Testing framework | Version: dev
Severity: Normal | Resolution:
Keywords: oracle, parallel, | Triage Stage: Accepted
tests |
Has patch: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Siddharth Panditrao):
Hi, I’ve been reading through the history of this ticket and the old PR to
understand why it was closed.
From what I can tell, the main issues earlier were:
* Dependency on ``expdp`` / ``impdp``
* Oracle-specific logic in the base backend
* Added complexity around cloning data
== Question / Idea ==
I was wondering if a simpler approach could work for Oracle:
* For parallel tests, create empty cloned test users (with suffixes like
``_1``, ``_2``)
* Skip exporting/importing data entirely
* Let Django handle schema creation via migrations and test data via its
existing serialization logic
This seems closer to how Django already handles parallel tests and avoids
external tools.
== Questions ==
I’m still learning Django internals, so I wanted to ask:
* Is empty schema cloning considered sufficient for Oracle?
* Would this be an acceptable direction to revisit this ticket, or is
there something I’m missing?
Happy to learn and adjust based on feedback. Thanks!
--
Ticket URL: <
https://code.djangoproject.com/ticket/31908#comment:4>