Feat: implement on_conflict

[izqalan]

What kind of change does this PR introduce?

Added on_conflict feature for insert method.

What is the current behavior?

Missing on_conflict feature for insert method. #78

What is the new behavior?

When inserting, if upsert: true and UNIQUE column specified on on_conflict: column option set on_conflict searchParams.

Additional context

http://postgrest.org/en/v7.0.0/api.html?highlight=on%20conflict#on-conflict

[soedirgo]

Hey again @izqalan! 👋

I just have a couple of nits while this is in a draft. Otherwise, looks good!

[izqalan]

@soedirgo updated with your suggestions.

[soedirgo]

Awesome, thanks again @izqalan!

[github-actions]

🎉 This PR is included in version 0.19.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[TomasHubelbauer]

Seems like this insert overload has since been deprecated (judging by the TypeScript types), use upsert like this:

await supabase.from('ips').upsert({ updated_at: new Date(), ip: request.ip, geo }, { onConflict: 'ip' });

[magick93]

How would I translate the following sql insert to the supabase js client?

INSERT INTO comment_votes (comment_id, user_id, vote)
VALUES('e9a8b088-aa2f-45ac-b961-e5b71cb5ef42','f1b80dc9-5830-432a-b137-d3c6b9ba2b4b', null) 
ON CONFLICT ON CONSTRAINT comment_votes_pkey
DO 
   UPDATE SET vote = excluded.vote;

Can I specify a composite key as a constraint for the conflict?

[steve-chavez]

@magick93 Replied on supabase/supabase#8093