#29757 closed Cleanup/optimization (fixed)
Document that easy connect string can be used to connect to pluggable databases on Oracle.
| Reported by: | Jani Tiainen | Owned by: | Jani Tiainen |
|---|---|---|---|
| Component: | Documentation | Version: | 2.1 |
| Severity: | Normal | Keywords: | oracle |
| Cc: | Mariusz Felisiak | Triage Stage: | Ready for checkin |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
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)))
Change History (8)
comment:2 by , 6 years ago
| Cc: | added |
|---|---|
| Summary: | Add simple support for service name as database credentials for Oracle backend → Document that easy connect string can be used to connect to pluggable databases on Oracle. |
| Triage Stage: | Unreviewed → Accepted |
| Type: | New feature → Cleanup/optimization |
Maybe a note/example in the https://docs.djangoproject.com/en/dev/ref/databases/#id11.
comment:3 by , 6 years ago
| Component: | Database layer (models, ORM) → Documentation |
|---|
comment:4 by , 6 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:6 by , 6 years ago
| Triage Stage: | Accepted → Ready for checkin |
|---|
Note:
See TracTickets
for help on using tickets.
Apparently there is possibility to use Oracle easy connect strings as well.
Maybe this could be documented in database specific documentation?