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

MSSQL upsert implementation - V3 backport #6875

Merged
merged 1 commit into from Nov 17, 2016

Conversation

4 participants
@harshithkashyap
Member

harshithkashyap commented Nov 17, 2016

Pull Request check-list

  • Does npm run test or npm run test-DIALECT pass with this change (including linting)?
  • Does your issue contain a link to existing issue (Closes #[issue]) or a description of the issue you are solving?
  • Have you added new tests to prevent regressions?
  • Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?
  • Have you added an entry under Future in the changelog?

Description of change

V3 backport #6842

@mention-bot

This comment has been minimized.

mention-bot commented Nov 17, 2016

@harshithkashyap, thanks for your PR! By analyzing the history of the files in this pull request, we identified @mbroadst, @BridgeAR and @sdepold to be potential reviewers.

@codecov-io

This comment has been minimized.

codecov-io commented Nov 17, 2016

Current coverage is 93.88% (diff: 98.24%)

Merging #6875 into v3 will increase coverage by 0.03%

Powered by Codecov. Last update 85238f6...2f9f172

@janmeier janmeier merged commit 9449c01 into sequelize:v3 Nov 17, 2016

4 checks passed

codecov/patch 98.24% of diff hit (target 93.85%)
Details
codecov/project 93.88% (+0.03%) compared to 85238f6
Details
continuous-integration/appveyor/pr AppVeyor build succeeded
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
@janmeier

This comment has been minimized.

Member

janmeier commented Nov 17, 2016

+ sequelize@3.26.0

@harshithkashyap harshithkashyap deleted the harshithkashyap:mssql-upsert-v3 branch Nov 17, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment