`diffEntitiesAtBlock` in the index-node API fails for immutable entities

[lutter]

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"
    }
  ]
}

[github-actions]

Looks like this issue has been open for 6 months with no activity. Is it still relevant? If not, please remember to close it.

[github-actions]

Looks like this issue has been open for 6 months with no activity. Is it still relevant? If not, please remember to close it.

[madumas]

Still relevant, and still reproducing today: we hit exactly this error on deployments with immutable entities (graph-node 0.42.1 on our side, and the same error on third-party indexers running 0.36.0 through 0.44.0 — so it is not version- or configuration-specific).

It would be genuinely useful to have this fixed: entityChangesInBlock is the cheapest way for an indexer to localise a POI divergence, and it is unavailable on every deployment using immutable entities.