Although I agree with you that sometimes it better to hide the complexity in
tnsnames.ora and/or sqlnet.ora, in todays world that’s not always possible
anymore. Mostly because access to the OS or file system as an application is
not guaranteed anymore. Not that this is anything new. Already back in 2007
when we developed a J2EE system for the financial industry (before my time at
Oracle) we would have wished for the connection string that we used in the
connection pools to be smarter.
Files unfortunately are not application runtime changes friendly, unless you
build the apps that way, which of course most folks don’t.
Thx,
Gerald
On May 8, 2019, at 23:59, Tim Hall <tim@xxxxxxxxxxxxxxx> wrote:
It kind-of ceases to be an "easy connect" if the EZ connect URL gets
too big though. :) It feels like it's better to commit to the
tnsnames.ora and sqlnet.ora and have a clean connect string. Just my
opinion though. :)
--
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.freelists.org_webpage_oracle-2Dl&d=DwIBaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=8iiVwrHSsTqnBrtY_Fuy-Gh9gb6TGuXFOB5tC6dNhvE&m=P0heWK4HY9Y-SRFFsPs9V2PvAxwyMVZ1u6gOZPniCs8&s=MsVyar-kkkeUtImA9vKquN2HqeIrpVNcz-6znAtAah8&e=
