David Lutterkort
David Lutterkort
When a write fails because Postgres is unhappy with it, e.g., because of an invalid block_range, it is very hard to understand what happened from the error message. This change...
This also removes some unrelated dead code and moves `sqlparser` to the workspace
When we resolve a single-object reference from the store, but find multiple children, we need to return an error. We did that already for derived fields, but for non-derived fields...
Our queries all ultimately get their data by doing something like `select to_jsonb(c.*) from ( ... complicated query ... ) c` because when these queries were written it was far...
### Description We should add a `graphman` command that checks that all shards can talk to each other in the way that we need. For each shard, it should access...
### Bug report With a schema like ```graphql type Parent @entity { id: Bytes! child: Child! } type Child @entity { id: Bytes! } ``` the result for a query...
When `graph-node` uses a shard that has asynchronous read replicas, query results are not deterministic because the read replicas can trail behind the main database, usually up to 30s. When...
### Description Aggregates can be formed either over the current bucket (hour, day) or the entire lifetime of the underlying timeseries. In some cases, it would also be useful to...
This crate exposes graph-node functionality for Node's N-API Currently it offers a single `validate_schema` function which returns schema validation errors.