kylefang/graphql-engine
1
0
Fork 0
mirror of https://github.com/zhigang1992/graphql-engine.git synced 2026-05-22 15:35:20 +08:00
Code Issues Packages Projects Releases Wiki Activity

update upsert column requirements in docs (#3413)

Browse Source
This commit is contained in:
Marion Schleifer
2019-11-25 10:35:36 +01:00
committed by Rikin Kachhia
parent 9dd0606128
commit 64eb726568
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/graphql/manual/mutations/upsert.rst
View File

@@ -44,15 +44,15 @@ The upsert functionality is sometimes confused with the update functionality. Ho
differently. An upsert mutation is used in the case when it's not clear if the respective row is already present
in the database. If it's known that the row is present in the database, ``update`` is the functionality to use.
For an upsert, **all columns need to be passed**.
**For an upsert, all columns that are necessary for an insert are required**.
**How it works**
1. Postgres tries to insert a row (hence all the columns need to be present)
1. Postgres tries to insert a row (hence all the required columns need to be present)
2. If this fails because of some constraint, it updates the specified columns
If not all columns are present, an error like ``NULL value unexpected for <not-specified-column>`` can occur.
If not all required columns are present, an error like ``NULL value unexpected for <not-specified-column>`` can occur.
Update selected columns on conflict