--- id: upsert title: 'Upsert data: upsert()' slug: upsert custom_edit_url: https://github.com/supabase/supabase/edit/master/spec/supabase_js_v1_legacy.yml --- import Tabs from '@theme/Tabs' import TabItem from '@theme/TabItem' Performs an UPSERT into the table. ```js const { data, error } = await supabase .from('messages') .upsert({ id: 3, message: 'foo', username: 'supabot' }) ``` ## Parameters ## Notes - Primary keys should be included in the data payload in order for an update to work correctly. - Primary keys must be natural, not surrogate. There are however, [workarounds](https://github.com/PostgREST/postgrest/issues/1118) for surrogate primary keys. ## Examples ### Upsert your data ```js const { data, error } = await supabase .from('messages') .upsert({ id: 3, message: 'foo', username: 'supabot' }) ``` ### Bulk Upsert your data ```js const { data, error } = await supabase.from('messages').upsert([ { id: 3, message: 'foo', username: 'supabot' }, { id: 4, message: 'bar', username: 'supabot' }, ]) ``` ### Upserting into tables with constraints Running the following will cause supabase to upsert data into the `users` table. If the username 'supabot' already exists, the `onConflict` argument tells supabase to overwrite that row based on the column passed into `onConflict`. ```js const { data, error } = await supabase .from('users') .upsert({ username: 'supabot' }, { onConflict: 'username' }) ``` ### Return the exact number of rows ```js const { data, error, count } = await supabase.from('users').upsert( { id: 3, message: 'foo', username: 'supabot', }, { count: 'exact', } ) ```