Closed scottfrederick closed 9 years ago
Alternatively, the Connector could support a jdbcUrl
field in credentials, and use that if it is present. If jdbcUrl
is not present, then fall back to looking for uri
or url
(which is what most managed database services provide) and transform the uri
into a JDBC URL as it does now.
OracleServiceInfo
builds a JDBC URL from the URI provided in the service credentials. The JDBC URL assumes that the path element from the credentials URI is a database name, and precedes it with a "/" in the JDBC URL (e.g.oracle://user:password@host:port/database
in credentials is transformed intojdbc:oracle:thin:user/password@host:port/database
)If the path element from the credentials URI is an SID instead of a database name, then it should be preceeded by a ":" in the JDBC URL instead (e.g.
oracle://user:password@host:port/sid
in credentials should be transformed intojdbc:oracle:thin:user/password@host:port:sid
).See https://community.oracle.com/thread/2290690.
Supporting both database name and SID might require additional fields in the credentials so
OracleServiceInfo
can get an indication of what the path element of the URI represents.