Reverse order of values when upserting #1317
Open
Conversation
This file contains 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
I contributed two tests to Rails because I was not sure how `insert_all` and `upsert_all` should behave with duplicate identifiers. For `insert_all`, all DBMS only insert the first value. For `upsert_all`, PostgreSQL throws an error in this scenario, but with sqlite and MySQL, the last entry ends up in the database. For now, I do not have a smarter idea than reversing the `inserts`, which ultimately provide the `values_list`. Adding `MAX` would be another, but I fear the SQL query would get much more complicated.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I contributed two tests to Rails because I was not sure how
insert_allandupsert_allshould behave with duplicate identifiers, but with different values in other columns.For
insert_all, all DBMS only insert the first value. Forupsert_all, PostgreSQL throws an error in this scenario, but with sqlite and MySQL, the last entry ends up in the database.For now, I do not have a smarter idea than reversing the
inserts, which ultimately provide thevalues_list. AddingMAXwould be another idea, but I fear the SQL query would get much more complicated.