#21775: No facility to specify the datafile of a django test Oracle tablespace
-------------------------------------+-------------------------------------
Reporter: smeatonj | Owner: alvaro@…
Type: New feature | Status: assigned
Component: Database layer | Version: 1.6
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: oracle | Needs documentation: 1
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by jarshwah):
https://github.com/django/django/pull/3118
This patch allows specifying the DATAFILE and MAXSIZE of each tablespace
(the primary and the tmp). The default maxsize has been increased from
200M to 500M to better support GIS on Oracle. This default may need to be
increased to correctly support GIS as it was just a guess - Shai to
confirm.
I've also changed the tablespace creation to be test_USER rather than
test_NAME - which should make more sense for an Oracle deployment. NAME
will be "xe" (or some other like-value) for every single django app
running on the same database, which could lead to clobbering if running
two different django applications on the same server. NAME will at least
be linked to the actual django application under test, rather than the
server.
--
Ticket URL: <https://code.djangoproject.com/ticket/21775#comment:6>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.bdc2b179b5ef1e5efb5e0d10bd4fe5b9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
