-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
fix(model): generate ON CONFLICT ... DO UPDATE correctly #11666
Conversation
Codecov Report
@@ Coverage Diff @@
## master #11666 +/- ##
=======================================
Coverage 96.26% 96.26%
=======================================
Files 94 94
Lines 9190 9190
=======================================
Hits 8847 8847
Misses 343 343
Continue to review full report at Codecov.
|
Do we know when this is going to be released? @sushantdhiman |
Today @Restuta |
👍 🎉 |
@sushantdhiman I see this one released https://github.com/sequelize/sequelize/releases/tag/v6.0.0-beta.4, any plans to release a patch for v5? |
Someone will have to backport that fix to target v5 branch |
@sushantdhiman I hope I did it right :) |
Pull Request check-list
Please make sure to review and check all of these items:
npm run test
ornpm run test-DIALECT
pass with this change (including linting)?npm run test-postgres
fails... with 3 unrelated failures (details) that occur both before and after my commit to fix bulkCreate generates incorrectON CONFLICT ... DO UPDATE
clause when model has > 1 primary key field and column names differ from field names #11665[ ] Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?[ ] Did you update the typescript typings accordingly (if applicable)?Description of change
Closes #11665