Fix issue where CustomConverter is ignored in table-driven feature mapping mode and provide exemplary implementations [3.5] #1665
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 PR fixes the table-driven mapping of feature types, which until now ignored custom converts.
Besides documentation, an exemplary implementation to map
BLOB
/bytea
columns as strings encoded in RFC 4648/2397 and large text columnsCLOB
/text
as strings is included.see #1668 for 3.6 version
Test setup
Oracle
PostgreSQL
Test requests
More example requests, which are too large for the description:
example_requests.txt
References