driver loading: provide loaded driver to Sequel::connect #34
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sequel::connect
will first attempt to auto-detect the driver based on thejdbc connection URI, and will fall-back to the driver given as
opts[:driver]
when auto-detection fails.
By memoizing the loaded driver from our previous
Sequel::JDBC::load_driver
and providing it to
Sequel::connect
, we provide one more chance for loadingto work.
This specifically seems to be the only path forward for Sybase drivers, whose
jdbc connection strings begin with
jdbc:sybase:Tds:
but use the driver withpath
com.sybase.jdbc4.jdbc.SybDriver
.