fix: Use PostgreSQL hex format for bytea literals (fixes #32) #71
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.
Summary
Fixes #32 - Bytea literals now use PostgreSQL-compatible hex format instead of invalid
b"..."syntax.Changes
encoding/heximport'\x...'hex formatbytesToOctets()functionfinal_coverage_test.goandedgecase_coverage_test.goImpact
High severity fix - Queries with byte values will now execute successfully instead of failing with syntax errors.
Before
After
Test plan
🤖 Generated with Claude Code