Repository navigation
Preserve raw token and NFT metadata in PostgreSQL bytea - #690
Open
startupcompliancekit wants to merge 1 commit into
Open
startupcompliancekit wants to merge 1 commit into
startupcompliancekit wants to merge 1 commit into
Conversation
This file contains hidden or 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
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.
Closes #590.
Store fungible-token names/symbols, NFT token URIs and collection URIs as PostgreSQL bytea. Preserve raw bytes during node ingestion and persistence, converting to UTF-8 strings at the API boundary. Migration 12 converts existing text with UTF-8 encoding.
Regression fixtures cover legacy text migration, raw NUL and malformed UTF-8 bytes, query round trips and API conversion. Validation: 18 tests across five suites passed against local PostgreSQL; production/test formatting and lint passed. No live node was used.
This targets the current master schema. If #685 is merged first, the companion integration patch also upgrades schema generation from 1 to 2; that combination passed 103 tests across 13 suites.