[PostgreSQL] No longer require restart after creating the database#467
Merged
loic-sharma merged 1 commit intomasterfrom Feb 9, 2020
Merged
[PostgreSQL] No longer require restart after creating the database#467loic-sharma merged 1 commit intomasterfrom
loic-sharma merged 1 commit intomasterfrom
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
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.
Npgsql, the PostgreSQL driver, caches the database's type information on the initial connection. This causes issues when BaGet creates the database as it adds the citext extension to support case insensitive columns. BaGet will now forcefully reload the database's types after migrations are run.
See: #442
See: npgsql/efcore.pg#170 (comment)