Reworking the Canyon Connector #38
Merged
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
…the process. The monster trasmute for get a mutable reference to a connect due to the Tiberius query method has been eliminated
…t of the configuration for a datasource
…rrowed to owned types in the structs that holds the user configuration
…on file, by giving them a unique spot
…orward to get rid out of the db_type property, since it will be inferred from the auth declaration
…ation file. The in-use per datasource database type will be inferred from the auth key
… authentication system
…arget to enable integrated auth for tiberius (MSSQL)
…talling their missing system headers
…ing the installation of the gssapi headers to the others UNIX based actions
…inker issues under msvc envs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 aims to rework the
Canyon Connector, which is the resposible for instanciate and store the database connections for the defined datasources targetted in the configuration file.Also, this closes #37 where we introduced a new configuration parameter to specify the kind of authorization which will be used in the SqlServer connections