Allow pgresult_stream_any to be used by sequel_pg#443
Merged
larskanis merged 1 commit intoged:masterfrom Mar 9, 2022
Merged
Conversation
sequel_pg needs to do it's on typecasting and column name mangling, and can do so by passing data through using a void *. This should not affect existing ruby-pg usage, and I expect the performance difference is not even measurable.
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
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.
sequel_pg needs to do its own typecasting and column name mangling,
and can do so by passing data through using a void *. This should
not affect existing ruby-pg usage, and I expect the performance
difference is not even measurable.
This can help sequel_pg work around the performance decrease when
using set_single_row_mode (#442).