Escaping Data for Data Types BOOLEAN / SUPER / GEOMETRY in Hash-Function #240
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.
Description
Taking correct data_type for ghost records and escaping hash-values for hashing function for data type boolean, geometry and super. These data types cannot be used in TRIM() function (in hashing-function)
Fixes #(issue)
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Configurate Hash-Columns with "is_hashdiff" with BOOLEAN / GEOMETRY / SUPER data types and create the stage. The error: function pg_catalog.btrim(boolean, "unknown") does not exist will occur.
Test Configuration:
Checklist: