[DRAFT] Support for PostgreSQL "RECORD" return types #2427
Closed
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
In this draft change, we've added support for PostgreSQL functions that return the "RECORD" data type.
|
Hey John, thanks for this! There was some work done (but not merged) to handle functions that return tables which may be similar to what you've done here: #1973. If you have a chance to take a look, let me know if you think there's redundancy. In any case, can you share an example schema and query you're using to develop this change? Or better yet, add a test case to |
|
Since it hasn't been updated in awhile I'm going to close this PR. We have some ideas for supporting composite types when using |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
In this draft change, we've added support for PostgreSQL functions that return the "RECORD" data type.