MySQL dialect: added implementation for upsert #5743
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
|
@kibertoad could you please have a look? |
kibertoad
approved these changes
Nov 28, 2023
|
thanks a lot! |
|
@kibertoad Hi, I see that the related PR in documentation is still open. Should we merge it maybe? Sorry, I don't know what's the right flow is. I mentioned it in the description btw. |
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.
Closes: #4769
Knex documentation update: knex/documentation#556
Done:
upsertimplementation for MySQLMySQL docs: https://dev.mysql.com/doc/refman/8.0/en/replace.html