-
-
Notifications
You must be signed in to change notification settings - Fork 192
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
Make OnConflict
store both update_columns
and values
#609
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @elbertronnie, thanks for contributing!! The implementation looks good to me :)
10cb9ff
to
038ec9b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@elbertronnie thank you! LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be nice to also add some doc tests
🎉 Released In 0.29.0 🎉Your participation is what makes us unique; your adoption is what drives us forward. |
🎉 Released In 0.29.1 🎉Thank you everyone for the contribution! |
PR Info
OnConflict::values
andOnConflict::update_columns
gets overridden by one another #593Breaking Changes
OnConflict::values
andOnConflict::update_columns
will append the new values keeping the old values intact instead of erasing themChanges
OnConflictUpdate
that determines the column update strategy in ON CONFLICT expressionsUpdateColumns
andUpdateExprs
withUpdate(Vec<OnConflictUpdate>)
inOnConflictAction