From 242e23ee3d69bb7fd3cf8051637ace626d4c9fd0 Mon Sep 17 00:00:00 2001 From: Ru Date: Tue, 13 Sep 2022 13:44:23 +0530 Subject: [PATCH] Update supabase_js_v1_legacy.yml Please see https://github.com/supabase/supabase-js/issues/550 --- spec/supabase_js_v1_legacy.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/spec/supabase_js_v1_legacy.yml b/spec/supabase_js_v1_legacy.yml index c5358848c23..8f106cac142 100644 --- a/spec/supabase_js_v1_legacy.yml +++ b/spec/supabase_js_v1_legacy.yml @@ -961,6 +961,7 @@ pages: 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. + - It is currently not possible to insert new data and update existing data at the same time. However, a [workaround](https://github.com/supabase/postgrest-js/issues/173#issuecomment-825124550) can be employed using Postgres functions/triggers. examples: - name: Upsert your data isSpotlight: true