-
Notifications
You must be signed in to change notification settings - Fork 12
transactions table: Store hash as BYTEA
#495
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
aditya1702
wants to merge
16
commits into
accountid-bytea-txns
Choose a base branch
from
hash-bytea
base: accountid-bytea-txns
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
c6682d5
Add HashBytea type for transaction hash BYTEA storage
aditya1702 6f73fdf
Update Transaction.Hash field to use HashBytea type
aditya1702 e743465
Wrap transaction hash in HashBytea in ConvertTransaction
aditya1702 5d16532
Use .String() for map key in IndexerBuffer
aditya1702 1ad897d
Update transactions.go for BYTEA hash storage
aditya1702 caacd85
Change transactions.hash column from TEXT to BYTEA
aditya1702 a041358
Add HashBytea unit tests
aditya1702 4c1e5dc
Update test files with valid 64-char hex hashes
aditya1702 09348d9
fix tests
aditya1702 d238b0b
add resolver for hash
aditya1702 d6526ef
Update statechanges.go
aditya1702 6ff993f
fix all tests
aditya1702 5058261
fix more tests
aditya1702 6477fa9
Update ingest_test.go
aditya1702 daa2999
Update internal/serve/graphql/resolvers/transaction_resolvers_test.go
aditya1702 396bb61
Update transaction_resolvers_test.go
aditya1702 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With the column type change from TEXT to BYTEA, invalid hex strings passed as
transactionHashfrom the GraphQL API now produce a driver-level error (fromHashBytea.Value()) instead of silently returning empty results. Consider adding input validation at the GraphQL/resolver layer before this reaches the DB.