Make RelationalTransactionRegistry extensible #280
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
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 makes it possible to specify a custom
IRelationalTransactionRegistryviaRelationalStoreConfiguration.This PR also makes
RelationalTransactionRegistry.WriteCurrentTransactionsvirtual so that you can override Nevermore's implementation to include other useful information.Breaking changes
ConnectionStringandMaxPoolSizeare no longer exposed byRelationalTransactionRegistryas they're duplicates of information already available viaRelationalStoreConfiguration.RelationalTransactionRegistrynow accepts the max SQL connection pool size via its constructor rather than the entire connection string, as that's all it actually needs.