Reimplement schema retrieval and scaffolding #59
Merged
Conversation
This file contains 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
|
@ChrisJollyAU While this still needs proper testing, I just scaffolded Northwind using this PR and it looks good to me. |
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.
Since we now allow users to use OLE DB or ODBC, the old schema retrieval code needed to be reimplemented, so that it is data access library agnostic (at least from a .NET dependency standpoint).
We now use either DAO or ADOX or a combination of both (the default) to get the database schema. The method used can be controlled by the
JetConnection.SchemaProviderTypeproperty.Base on the new schema retrieval code, the scaffolder was completely rewritten as well.
Addresses #55, #56, #57 and #58