#27435: Raise an error when using --keepdb without an explicit TEST.PASSWORD on
Oracle
-----------------------------------+------------------------------------
Reporter: Simon Charette | Owner: nobody
Type: Bug | Status: new
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 Shai Berger):
Replying to [comment:4 Simon Charette]:
> @felixxm
>
> > I think that the best solution will be to set up password randomly
every time where it's not set and we use --keepdb flag:
>
> I'm not too familar with Oracle's authentication management but how are
you going to re-connect to the kept database on the second run if you
generate a random on the first one?
>
I'm glad to see it wasn't just me who missed @felixx's intention...
He suggested that we use our administrative user to change the test user's
password to a new random password on each run. I think this is a better
solution.
--
Ticket URL: <https://code.djangoproject.com/ticket/27435#comment:5>
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.511627ad01ae7c04d03e74a5ff64e203%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
