You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by beacoding February 20, 2023
Looks like we cannot specify an onConflict and where together when we set a partial index on our postgres db.
We end up getting a unique or exclusion constraint matching the ON CONFLICT when a partial index is used and we specify the key to use it for.
Discussed in supabase/supabase#12565
Originally posted by beacoding February 20, 2023
Looks like we cannot specify an
onConflict
andwhere
together when we set a partial index on our postgres db.We end up getting a
unique or exclusion constraint matching the ON CONFLICT
when a partial index is used and we specify the key to use it for.The solution to fix this is to filter on the index_predicate, but the client does not allow us to do this
https://stackoverflow.com/questions/42022362/no-unique-or-exclusion-constraint-matching-the-on-conflict
Are there any plans to support upserts of partial indices?
The text was updated successfully, but these errors were encountered: