Update Postgres adapter docs #654
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
|
It is a relic from the past but we decided to keep in case we need to add extensions in the future. Perhaps we keep the function public but we no longer refer to it in the docs? |
|
Ah got it! Done. For some context, I was reading this thread here and trying to think of how to help clarify things and I noticed some people thought |
|
Maybe I should add a note to the function doc that says there are currently no Ecto defined extensions but there may be in the future? |
josevalim
approved these changes
Feb 21, 2025
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.
Ecto.Adapters.Postgres.extensions()looks to me like a relic from the past that is no longer applicable. But please let me know if I'm missing something.