Rakesh Emmadi 5bafdce9a3 fix delete mutation returning incorrect data (fix #1794) (fix #1763) (#1827) ...

From `alpha-40` we've been using a `WHERE` clause to fetch required rows and generate mutation response. This has a few limitations like the requirement of a primary key/unique constraint. This also returns inconsistent data on `delete` mutation as mentioned in #1794. 
Now, we're using `VALUES (..)` (refer [here](https://www.postgresql.org/docs/current/sql-values.html)) expression to form virtual table rows in `SQL` to generate mutation response.

Internal changes:-
- Not to use primary key/unique constraint columns:-
  - Revert back to `ConstraintName` from `TableConstraint` in `TableInfo` type
  - Remove `tcCols` field in `TableConstraint` type
  - Modify `table_info.sql` and `fetchTableMeta` function `SQL`
- A test case to perform `delete` mutation and returning relational objects.

2019-03-22 12:38:42 +05:30

..

schema-metadata-api

update operators in metadata api docs (#1610)

2019-02-15 18:18:18 +05:30

index.rst

docs update (#1535)

2019-02-06 12:09:36 +05:30

mutation.rst

fix delete mutation returning incorrect data (fix #1794) (fix #1763) (#1827)

2019-03-22 12:38:42 +05:30

pgtypes.csv

add docs for schema / metadata api (close #409) (#626)

2018-10-08 19:42:03 +05:30

postgresql-types.rst

add table of contents to docs pages (#1115)

2018-12-03 17:42:24 +05:30

query.rst

docs update (#1535)

2019-02-06 12:09:36 +05:30