docs: Update examples to use pgx/v5 #2863
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
andrewmbenton
force-pushed
the
andrew/docs-default-pgx
branch
from
e472751
to
196a419
Compare
andrewmbenton
force-pushed
the
andrew/docs-default-pgx
branch
from
196a419
to
5145179
Compare
kyleconroy
approved these changes
Oct 17, 2023
This pull request was closed.
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.
I'm not sure that we should update all of these examples to use
pgx/v5, but let me know what you think. I walked back a change to the example where we explicitlyPreparequeries since I didn't want to deal with a custom enum issue.