#27435: Raise an error when using --keepdb without an explicit TEST.PASSWORD on
Oracle
-----------------------------------+------------------------------------
Reporter: Simon Charette | Owner: felixxm
Type: Bug | Status: assigned
Component: Testing framework | Version: 1.10
Severity: Release blocker | Resolution:
Keywords: oracle | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+------------------------------------
Comment (by felixxm):
Replying to [comment:10 Simon Charette]:
> > I think that the problem may be in the ALTER USER permission missing.
It's hard to say without error details.
>
> This ticket might be invalid as I didn't reproduce the error myself. Are
we sure that `--keepdb` actually works when no test password is defined?
Or is the database simply dropped by the admin user if we can't connect to
it on the second run?
If administrative user has `DBA` permission (which includes `ALTER USER`)
then `test` works properly with `--keepdb` option. I checked this few
times. IMO this ticket should be close.
--
Ticket URL: <https://code.djangoproject.com/ticket/27435#comment:11>
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/067.4abaa01ff161720c60c6d7582710f674%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
