Implement Upsert [#482] #882
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Problem Apps need the ability to insert or, if the row already exists, update the existing row. This is commonly called "upsert" and is [documented for SQLite here](https://www.sqlite.org/lang_UPSERT.html). The existing "replace" on conflict clause for `insert()` often does not have the desired behavior. It will cascade (with deletes, if specified) along foreign keys if the value exists and has to be replaced ([see Issue 842](stephencelis#842)). # Solution Create an `upsert()` method for queries. The basic form allows for the fallback setters to be manually specified. A slightly more ergonomic version will compute the setters from the inserted values by removing the "conflicting" column, and then using the inserted values via the "excluded" qualifier. Additionally, an `Encodable` version of `upsert` is provided.
Contributor
Author
|
Travis is failing on the macOS builds because it is using High Sierra instead of Mojave. UPSERT syntax was added to SQLite with version 3.24.0 (2018-06-04). However, macOS apparently didn't include that version until Mojave, and iOS until 12.0. It might be possible to use |
|
since the main repo looks dead, did you by any chance keep an updated fork with this patch? |
Contributor
Author
|
I don't, sorry. |
|
@andyfinnell at the end I found another fork with this PR and others merged, so I switched there; thank you for your work :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Apps need the ability to insert or, if the row already exists, update the existing row. This is commonly called "upsert" and is documented for SQLite here. The existing "replace" on conflict clause for
insert()often does not have the desired behavior. It will cascade (with deletes, if specified) along foreign keys if the value exists and has to be replaced (see Issue 842).Solution
Create an
upsert()method for queries. The basic form allows for the fallback setters to be manually specified. A slightly more ergonomic version will compute the setters from the inserted values by removing the "conflicting" column, and then using the inserted values via the "excluded" qualifier. Additionally, anEncodableversion ofupsertis provided.