mirror of
https://github.com/hasura/graphql-engine.git
synced 2024-12-24 07:52:14 +03:00
a3fc1889bb
…rking metadata operations And add an initial benchmark for replace_metadata, to unblock some performance improvements to that op in a PR to be merged after this. This is an MVP just to have something in CI to reference when optimizing metadata operations. See TODO for roadmap. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/3673 Co-authored-by: jkachmar <8461423+jkachmar@users.noreply.github.com> GitOrigin-RevId: 968d1f92ca79c78ad90b2304d2214069bc739621 |
||
---|---|---|
.. | ||
adhoc_operations | ||
config.query.yaml | ||
dump.sql.gz | ||
README.md | ||
replace_metadata.json |
This is the classic chinook data set, which simulates a simple digital media store; with dozen or so tables, some simple relationships, and (depending on the table) a few dozen to a few hundred rows of realistic data per table.
Additionally it has been enriched with some sensible permissions on two new roles: employee, and customer.
Selected for inclusion because it's understandable, standard, familiar and somewhat realistic.