Add PG::TextEncoder::Bytea to BasicTypeRegistry #506
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
This encoder used to be excluded from the registry, since it's the only encoder that has a negative performance implication. However it should be there for completeness and because it's valueable for sending data per COPY command to the server. Another issue was, that we supported PostgreSQL-8.4 to the time TextEncoder::Bytea was implemented, but the hex bytea format was introduced with PostgreSQL-9.0. Now we don't support such old versions any longer, so that the encoder can be used bar none.
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.
This encoder used to be excluded from the registry, since it's the only encoder that has a negative performance implication. However it should be there for completeness and because it's valuable for sending data per COPY command to the server.
Another issue was, that we supported PostgreSQL-8.4 to the time TextEncoder::Bytea was implemented, but the hex bytea format was introduced with PostgreSQL-9.0. Now we don't support such old versions any longer, so that the encoder can be used bar none.