Since getDriver is a string why not just change the javadoc and
implementation such that it accepts either?
if (isURI(s)) {
}
That way it will keep on keeping on for the volk that are already using it.
Maybe on top of that we use the actual types we want instead of strings,
like java.net.URI and have overloads?
From: Christofer Dutz <[email protected]>
<[email protected]>
Reply: [email protected] <[email protected]> <[email protected]>
Date: June 30, 2021 at 13:57:15
To: [email protected] <[email protected]> <[email protected]>
Subject: [DISCUSS] Change the semantics of "getDriver"?
Hi all,
while working on streamlining the API and making it more tool-friendly,
I added a "listDrivers" method that returns the codes for all drivers
currently registered in the DriverManager. I noticed that we have a
"getDriver" method, that accepts a full url. However it's only
interested in the scheme part of the URL.
Would you have any objections to me changing this to "getDriver" being
defined on the "code" only and to add a "getDriverForUrl" to take over
the function of the current getDriver" implementation?
Chris
