Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -511,15 +511,15 @@ The `indexerHints` setting in a Subgraph's manifest provides directives for inde

History as of a given block is required for:

- [Time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the Subgraph's history
- Using the Subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another Subgraph, at that block
- [Time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries-example), which enable querying the past states of these entities at specific blocks throughout the Subgraph's history
- Using the Subgraph as a [graft base](/subgraphs/developing/creating/advanced/#grafting-onto-existing-subgraphs) in another Subgraph, at that block
- Rewinding the Subgraph back to that block

If historical data as of the block has been pruned, the above capabilities will not be available.

> Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data.

For Subgraphs leveraging [time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your Subgraph's settings:
For Subgraphs leveraging [time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries-example), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your Subgraph's settings:

To retain a specific amount of historical data:

Expand All @@ -539,13 +539,13 @@ indexerHints:

| Version | Release notes |
| :-: | --- |
| 1.3.0 | Added support for [Subgraph Composition](/cookbook/subgraph-composition-three-sources) |
| 1.2.0 | Added support for [Indexed Argument Filtering](/developing/creating/advanced/#indexed-argument-filters--topic-filters) & declared `eth_call` |
| 1.1.0 | Supports [Timeseries & Aggregations](/developing/creating/advanced/#timeseries-and-aggregations). Added support for type `Int8` for `id`. |
| 1.0.0 | Supports [`indexerHints`](/developing/creating/subgraph-manifest/#indexer-hints) feature to prune Subgraphs |
| 1.3.0 | Added support for [Subgraph Composition](/subgraphs/guides/subgraph-composition/) |
| 1.2.0 | Added support for [Indexed Argument Filtering](/subgraphs/developing/creating/advanced/#indexed-argument-filters--topic-filters) & declared `eth_call` |
| 1.1.0 | Supports [Timeseries & Aggregations](/subgraphs/developing/creating/advanced/#timeseries-and-aggregations). Added support for type `Int8` for `id`. |
| 1.0.0 | Supports [`indexerHints`](/subgraphs/developing/creating/subgraph-manifest/#indexer-hints) feature to prune Subgraphs |
| 0.0.9 | Supports `endBlock` feature |
| 0.0.8 | Added support for polling [Block Handlers](/developing/creating/subgraph-manifest/#polling-filter) and [Initialisation Handlers](/developing/creating/subgraph-manifest/#once-filter). |
| 0.0.7 | Added support for [File Data Sources](/developing/creating/advanced/#ipfsarweave-file-data-sources). |
| 0.0.8 | Added support for polling [Block Handlers](/subgraphs/developing/creating/subgraph-manifest/#polling-filter) and [Initialisation Handlers](/subgraphs/developing/creating/subgraph-manifest/#once-filter). |
| 0.0.7 | Added support for [File Data Sources](/subgraphs/developing/creating/advanced/#ipfsarweave-file-data-sources). |
| 0.0.6 | Supports fast [Proof of Indexing](/indexing/overview/#what-is-a-proof-of-indexing-poi) calculation variant. |
| 0.0.5 | Added support for event handlers having access to transaction receipts. |
| 0.0.4 | Added support for managing subgraph features. |
Original file line number Diff line number Diff line change
Expand Up @@ -102,6 +102,7 @@ After running this command, the CLI will ask for a version label.

- It's strongly recommended to use [semver](https://semver.org/) for versioning like `0.0.1`. That said, you are free to choose any string as version such as `v1`, `version1`, or `asdf`.
- The labels you create will be visible in Graph Explorer and can be used by curators to decide if they want to signal on a specific version or not, so choose them wisely.
- Version labels must be unique within a Subgraph: deploying with a label that already exists fails with a `Version label already exists` error, so use a new label for each deployment.

## Testing Your Subgraph

Expand Down
2 changes: 2 additions & 0 deletions website/src/pages/en/subgraphs/querying/graphql-api.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -100,6 +100,8 @@ When querying a collection, it is best to:
- Use the `skip` parameter to skip entities and paginate. For instance, `first:100` shows the first 100 entities and `first:100, skip:100` shows the next 100 entities.
- Avoid using `skip` values in queries because they generally perform poorly. To retrieve a large number of items, it's best to page through entities based on an attribute as shown in the previous example above.

> Note: If `first` is not specified, collection queries return at most 100 entities. The maximum value for `first` is 1000 (the Graph Node default, set by `GRAPH_GRAPHQL_MAX_FIRST`); requesting more returns an error. To retrieve more entities, paginate as shown in the examples below.

#### Standard Pagination Example

```graphql
Expand Down
Loading