-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add on_conflict for upsert #8
Comments
Create @OnConflict annotation that allow to be in the both with prior Criteria > Repository |
Merged
arnaud-thorel-of
added a commit
that referenced
this issue
Jul 24, 2024
* feat(null): upsert and onConflict Issues : - #3 Upsert does not really upsert - #8 add on_conflict for upsert * feat: add upsert methods with onconflict --------- Co-authored-by: jthoreux <[email protected]>
arnaud-thorel-of
added a commit
that referenced
this issue
Jul 25, 2024
…upserts (#39) Issues : - #3 Upsert does not really upsert - #8 add on_conflict for upsert Co-authored-by: jthoreux <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Requested feature
We need to use "on_conflict" parameter for upsert.
Like this: https://postgrest.org/en/v10.0/api.html?highlight=merge#on-conflict
Proposal
The text was updated successfully, but these errors were encountered: