mirror of
https://github.com/hasura/graphql-engine.git
synced 2024-12-17 12:31:52 +03:00
5bafdce9a3
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. |
||
|---|---|---|
| .. | ||
| Permission | ||
| Relationship | ||
| Schema | ||
| Deps.hs | ||
| Headers.hs | ||
| Metadata.hs | ||
| Permission.hs | ||
| QueryTemplate.hs | ||
| Relationship.hs | ||
| RemoteSchema.hs | ||
| Subscribe.hs | ||
| Utils.hs | ||