graphql-engine/server/tests-py/queries/graphql_query/v1alpha1/errors/teardown.yaml

type: bulk
args:

#Drop relationship first
- type: drop_relationship
  args:
    relationship: articles
    table:
      schema: public
      name: author
    
- type: run_sql
  args:
    sql: |
      drop table article;
      drop table author;
      drop table "user";

#- type: run_sql
#  args:
#    sql: |
#      drop type inventory_item
introduce v1/graphql (fix #1368) (#2064) Changes compared to `/v1alpha1/graphql` * Changed all graphql responses in /v1/graphql endpoint to be 200. All graphql clients expect responses to be HTTP 200. Non-200 responses are considered transport layer errors. * Errors in http and websocket layer are now consistent and have similar structure. 2019-05-10 09:05:11 +03:00			`type: bulk`
			`args:`

			`#Drop relationship first`
			`- type: drop_relationship`
			`args:`
			`relationship: articles`
			`table:`
			`schema: public`
			`name: author`

			`- type: run_sql`
			`args:`
			`sql: \|`
Integration test improvements (for speed/clarity), also increase polling interval for scheduled events This claws back ~7min from integration tests (run serially, as with `dev.sh test --integration` Further improvements would do well to focus on optimizing metadata operations, as `setup` dominates GitOrigin-RevId: 76637d6fa953c2404627c4391447a05bf09355fa 2021-04-27 08:34:14 +03:00			`drop table article;`
			`drop table author;`
			`drop table "user";`
introduce v1/graphql (fix #1368) (#2064) Changes compared to `/v1alpha1/graphql` * Changed all graphql responses in /v1/graphql endpoint to be 200. All graphql clients expect responses to be HTTP 200. Non-200 responses are considered transport layer errors. * Errors in http and websocket layer are now consistent and have similar structure. 2019-05-10 09:05:11 +03:00
			`#- type: run_sql`
			`# args:`
			`# sql: \|`
			`# drop type inventory_item`