#25899: manage.py tests requires database creation privileges
-------------------------------+--------------------
Reporter: JorisBenschop | Owner: nobody
Type: New feature | Status: new
Component: Uncategorized | Version: 1.9
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------
From
{{{
#https://docs.djangoproject.com/en/1.9/topics/testing/overview/#the-test-
database
By default the test databases get their names by prepending test_ to the
value of the NAME settings for the databases defined in DATABASES.
}}}
I guess this works great on sqlite and my homegrown postgres machine, but
I'm developing applications on Oracle RAC clusters, and I hope you can see
this is not an environment I'd be allowed to create databases on. The
database schemas are rather complex (using things like RAW(16) primary
keys and reference-based partitioning) and I'm not allowing Django to make
the tables itself.
I have been unable to find a workaround in documentation (e.g. --use-this-
database-instead-of-creating-one= and --assume-models-are-present ). If
this exists, please change this ticket into a documentation request
instead.
--
Ticket URL: <https://code.djangoproject.com/ticket/25899>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/056.4014d2cc675d4361535c3bde7a7973fa%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
