#29757: Add simple support for service name as database credentials for Oracle
backend
-------------------------------------+-------------------------------------
Reporter: Jani | Owner: nobody
Tiainen |
Type: New | Status: new
feature |
Component: Database | Version: 2.1
layer (models, ORM) |
Severity: Normal | Keywords: oracle
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Oracle 12c with pluggable databases uses service name instead of service
id (sid) to connect to database if PORT is provided.
Without port connection uses tnsnames.ora definitions or full DSN string
in name
Django code uses only sid when port is defined (3rd parameter of
{{{makedsn(...)}}} call)
{{{makedsn(...)}}} call has additional parameter {{{service_name}}} (4th
parameter)
It's a bit inconvenient to build full DSN string for connection.
Sample full DSN string:
{{{
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=foobar)))
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29757>
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/048.4a83cf8ff94c4002c6b8c04f754218a3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
