graphql-engine/server/tests-py/queries/graphql_query/caching/setup.yaml

type: bulk
args:

- type: run_sql
  args:
    sql: |
      CREATE TABLE users (id serial PRIMARY KEY, name text NOT NULL);
      INSERT INTO users (name) VALUES ('Alyssa'), ('Ben');

- type: track_table
  args: users
Track variable uses within query validation for caching (fix #3097) (#3135) This fix is a little ugly, but it’s the only simple solution without a significant refactoring that restructures the relationship between GraphQL/Validate and GraphQL/Resolve. The ugliness should go away if we implement something like #2801. 2019-10-16 17:33:34 +03:00			`type: bulk`
			`args:`
[server] coalesce multiple run_sql calls in tests (#270) GitOrigin-RevId: abd7303aaf8e7a8739fd10574249aec450082ef8 2021-01-06 19:06:24 +03:00
Track variable uses within query validation for caching (fix #3097) (#3135) This fix is a little ugly, but it’s the only simple solution without a significant refactoring that restructures the relationship between GraphQL/Validate and GraphQL/Resolve. The ugliness should go away if we implement something like #2801. 2019-10-16 17:33:34 +03:00			`- type: run_sql`
			`args:`
			`sql: \|`
			`CREATE TABLE users (id serial PRIMARY KEY, name text NOT NULL);`
			`INSERT INTO users (name) VALUES ('Alyssa'), ('Ben');`
[server] coalesce multiple run_sql calls in tests (#270) GitOrigin-RevId: abd7303aaf8e7a8739fd10574249aec450082ef8 2021-01-06 19:06:24 +03:00
Track variable uses within query validation for caching (fix #3097) (#3135) This fix is a little ugly, but it’s the only simple solution without a significant refactoring that restructures the relationship between GraphQL/Validate and GraphQL/Resolve. The ugliness should go away if we implement something like #2801. 2019-10-16 17:33:34 +03:00			`- type: track_table`
			`args: users`