Register PG extensions in the model by convention #2161
Merged
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.
By scanning property types in the model.
@AndriySvyryd, this adds two ModelFinalizing conventions which scan all properties, get their type mappings, and for certain supported types that are known to require PostgreSQL extensions, adds those to the model. Up to now users have had to add these explicitly. Any intuition on whether this is problematic perf-wise?
Closes #2137