refactor: save only one txi for aex9 presence #777
Merged
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.
What
:derive_aex9_presence
with:update_aex9_state
txi
from key to valueWhy
:update_aex9_state
type for a contract call is de-duplicated if enqueued right afterwards an async task created for a contract create.txi
without deleting other record (only the last value is used on aex9 endpoints)./aex9/balances/account
returning duplicates #735Validation steps
Run the migration bellow and access:
http://localhost:4000/aex9/balances/account/ak_CNcf2oywqbgmVg3FfKdbHQJfB959wrVwqfzSpdWVKZnep7nj4
It shall return deduped entries (around 30).