Description
Modern JDBC drivers do not require explicit init through Class.forName. Instead, it works as follows:
1) java.sql.Driver file is created under META-INF/services directory.
2) Driver has static initializer which registers itself within DriverManager.
We should do that for both think and new thin drivers, and remove all Class.forName calls from tests afterwards.
Attachments
Issue Links
- Is contained by
-
IGNITE-4922 JDBC Driver: renew thin client based solution
-
- Resolved
-
- links to
