graphprotocol / graphprotocol/graph-node
`diffEntitiesAtBlock` in the index-node API fails for immutable entities
Open
Nobody has claimed this yet.
bug
index-node API
Stale
- Dominant language
- Rust
- Stars
- 3.2k
- Forks
- 1.1k
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 1
Description
In a subgraph that uses immutable entities, the following query fails:
{
entityChangesInBlock(subgraphId: "<some id>", blockNumber: 1234){
updates {
entities
type
}
deletions {
entities
type
}
}
}
The error is
{
"errors": [
{
"message": "Store error: store error: column \"block_range\" does not exist"
}
]
}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the entityChangesInBlock query against a subgraph that uses immutable entities, then trace the index-node API handling for diffEntitiesAtBlock. Done means the query succeeds and returns the expected updates and deletions without the missing block_range error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, rust
- Domain
- api, backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100