#30307: dbshell doesn't pass password properly on Oracle 18c.
-------------------------------------+-------------------------------------
Reporter: Mark Gordon | Owner: msg555@…
Type: Bug | Status: assigned
Component: Database layer | Version: 2.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: oracle dbshell | Triage Stage: Accepted
runshell |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by felixxm):
I'm really sure that previous solution worked properly with `sqlplus` for
Oracle 11.2 and 12.1, it has been also confirmed also by Shane Allgeier
who reported #29199.
There is a test to check new format in the (`test_password_with_at_sign`),
we resigned from creating dynamically a custom Oracle user etc. to check
this.
I double-checked and can confirmed that format without backslashes works
for Oracle 12.2 and 18c so changes in `django/db/backends/oracle/base.py`
looks good.
--
Ticket URL: <https://code.djangoproject.com/ticket/30307#comment:4>
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/064.25713326f0c647fcfe648b7af1da4876%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
