graphql-engine/server/tests-py/queries/graphql_query/basic/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

- type: run_sql
  args:
    sql: |
      drop table author

- type: run_sql
  args:
    sql: |
      drop table "user"
python based tests (#387) 2018-09-18 09:21:57 +03:00			`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`
add python based tests, remove haskell tests this does not generate coverage report yet 2018-10-04 15:44:15 +03:00
python based tests (#387) 2018-09-18 09:21:57 +03:00			`- type: run_sql`
			`args:`
			`sql: \|`
			`drop table author`
add python based tests, remove haskell tests this does not generate coverage report yet 2018-10-04 15:44:15 +03:00
breaking: encode bigint and bigserial postgres types as strings in response (fix #633) (#640) This is breaking change where bigint and bigserial Postgres types will be encoded as GraphQL String types, as opposed to Int as present in earlier releases. Input types were already encoded as String. This is achieved by selecting `bigint` and `bigserial` columns as `text`s in the SQL query: `select "big_id"::text ..` instead of `select "big_id" .. `. Reason for that change is outlined in #633 where JavaScript cannot decode 64 bit Integers. 2018-10-05 08:16:21 +03:00			`- type: run_sql`
			`args:`
			`sql: \|`
			`drop table "user"`