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
..
DML.hs	fix delete mutation returning incorrect data (fix #1794) (fix #1763) (#1827)	2019-03-22 12:38:42 +05:30
GeoJSON.hs	refactor to remove warnings especially with orphan instances (#1163)	2018-12-13 12:56:15 +05:30
Rewrite.hs	fix delete mutation returning incorrect data (fix #1794) (fix #1763) (#1827)	2019-03-22 12:38:42 +05:30
Time.hs	refactor to remove warnings especially with orphan instances (#1163)	2018-12-13 12:56:15 +05:30
Types.hs	breaking: correct (de)serialisation of postgres numeric types in json (fix #1523) (#1662)	2019-03-01 17:15:04 +05:30
Value.hs	fix mutation returning when relationships are present (fix #1576) (#1703)	2019-03-07 15:54:07 +05:30