{"id": "json_api:tableupsertview", "page": "json_api", "ref": "tableupsertview", "title": "Upserting rows", "content": "An upsert is an insert or update operation. If a row with a matching primary key already exists it will be updated - otherwise a new row will be inserted. \n                 The upsert API is mostly the same shape as the  insert API . It requires both the  insert-row  and  update-row  permissions. \n                 POST /<database>/<table>/-/upsert\nContent-Type: application/json\nAuthorization: Bearer dstok_<rest-of-token> \n                 {\n    \"rows\": [\n        {\n            \"id\": 1,\n            \"title\": \"Updated title for 1\",\n            \"description\": \"Updated description for 1\"\n        },\n        {\n            \"id\": 2,\n            \"description\": \"Updated description for 2\",\n        },\n        {\n            \"id\": 3,\n            \"title\": \"Item 3\",\n            \"description\": \"Description for 3\"\n        }\n    ]\n} \n                 Imagine a table with a primary key of  id  and which already has rows with  id  values of  1  and  2 . \n                 The above example will: \n                 \n                     \n                         Update the row with  id  of  1  to set both  title  and  description  to the new values \n                     \n                     \n                         Update the row with  id  of  2  to set  title  to the new value -  description  will be left unchanged \n                     \n                     \n                         Insert a new row with  id  of  3  and both  title  and  description  set to the new values \n                     \n                 \n                 Similar to  /-/insert , a  row  key with an object can be used instead of a  rows  array to upsert a single row. \n                 If successful, this will return a  200  status code and a  {\"ok\": true}  response body. \n                 Add  \"return\": true  to the request body to return full copies of the affected rows after they have been inserted or updated: \n                 {\n    \"rows\": [\n        {\n            \"id\": 1,\n            \"title\": \"Updated title for 1\",\n            \"description\": \"Updated description for 1\"\n        },\n        {\n            \"id\": 2,\n            \"description\": \"Updated description for 2\",\n        },\n        {\n            \"id\": 3,\n            \"title\": \"Item 3\",\n            \"description\": \"Description for 3\"\n        }\n    ],\n    \"return\": true\n} \n                 This will return the following: \n                 {\n    \"ok\": true,\n    \"rows\": [\n        {\n            \"id\": 1,\n            \"title\": \"Updated title for 1\",\n            \"description\": \"Updated description for 1\"\n        },\n        {\n            \"id\": 2,\n            \"title\": \"Item 2\",\n            \"description\": \"Updated description for 2\"\n        },\n        {\n            \"id\": 3,\n            \"title\": \"Item 3\",\n            \"description\": \"Description for 3\"\n        }\n    ]\n} \n                 When using upsert you must provide the primary key column (or columns if the table has a compound primary key) for every row, or you will get a  400  error: \n                 {\n    \"ok\": false,\n    \"errors\": [\n        \"Row 0 is missing primary key column(s): \\\"id\\\"\"\n    ]\n} \n                 If your table does not have an explicit primary key you should pass the SQLite  rowid  key instead. \n                 Pass  \"alter: true  to automatically add any missing columns to the table. This requires the  alter-table  permission.", "breadcrumbs": "[\"JSON API\", \"The JSON write API\"]", "references": "[]"}