Implement automatic driver (ODBC) and provider (OLE DB) inference and detection #47
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lauxjpn
force-pushed
the
feature/provider_detection
branch
from
84aafe4 to
bdfbafa
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR allows to specify just a file name or path as the connection string or omit the driver (ODBC) or provider (OLE DB) part of the connection string.
In those cases, the driver/provider with the most recent version of all installed compatible drivers/providers will be used.
If just a file name is used,
JetConfiguration.DefaultDataAccessProviderTypewill be used as the provider type.Addresses #45 (comment)
This PR also uses a nightly-build of
System.Data.OleDb, that works inside of x86 processes. See dotnet/runtime#33899 for further details.