fix hex bit strings with leading zeroes in postgresql #51375
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.
Motivation / Background
Currently when casting a hex string argument for a PostgreSQL
bit
orbit_varying
column, leading zeroes are discarded. This is unexpected, and differs from the behavior of binary strings.Detail
This Pull Request ensures leading zeroes are preserved, e.g. assigning a bit string column "0x5F" results in the bit string "01011111" instead of "1011111" being sent to Postgres.
Additional information
Checklist
Before submitting the PR make sure the following are checked:
[Fix #issue-number]