Skip to content
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

Upsert does not really upsert #3

Closed
antoinebesnardof opened this issue Jan 11, 2024 · 0 comments · Fixed by #36
Closed

Upsert does not really upsert #3

antoinebesnardof opened this issue Jan 11, 2024 · 0 comments · Fixed by #36

Comments

@antoinebesnardof
Copy link
Contributor

antoinebesnardof commented Jan 11, 2024

Description

The PostgrestRepository#upsert(List) method does not really upsert values. It actually acts like a post() or create() but does not update existing values.

Proposal

  • Create a post(List) or create(List) method in Repository interface
  • Implement this newly created method with the current PostgrestRepository#upsert(List) behavior
  • Defaultly append value "resolution=merge-duplicates" to the "Prefer: " header in the PostgrestRepository#upsert(List) method

julienTho added a commit that referenced this issue Jul 23, 2024
Issues :
- #3 Upsert does not really upsert
- #8 add on_conflict for upsert
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]>
julienTho added a commit that referenced this issue Jul 25, 2024
…upserts

Issues :
- #3 Upsert does not really upsert
- #8 add on_conflict for upsert
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
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant