Rakesh Emmadi 5f274b5527 fix mutation returning when relationships are present (fix #1576) (#1703) ... If returning field contains nested selections then mutation is performed in two steps 1. Mutation is performed with returning columns of any primary key and unique constraints 2. returning fields are queried on rows returned by selecting from table by filtering with column values returned in Step 1. Since mutation takes two courses based on selecting relations in returning field, it is hard to maintain sequence of prepared arguments (PrepArg) generated while resolving returning field. So, we're using txtConverter instead of prepare to resolve mutation fields.		2019-03-07 15:54:07 +05:30
..
delete	conform to graphql subscription and error spec (close #1056, close #1059) (#1126)	2018-12-04 19:07:38 +05:30
insert	fix mutation returning when relationships are present (fix #1576) (#1703)	2019-03-07 15:54:07 +05:30
update	support column presets in update mutation (closes #1449, closes #1464) (#1473)	2019-02-11 18:15:30 +05:30