Skip to content

docs: fix confusion of upsert's return value when using MySQL and Mar…#11093

Merged
sushantdhiman merged 1 commit intosequelize:masterfrom
LittleSaya:master
Jun 21, 2019
Merged

docs: fix confusion of upsert's return value when using MySQL and Mar…#11093
sushantdhiman merged 1 commit intosequelize:masterfrom
LittleSaya:master

Conversation

@LittleSaya
Copy link
Copy Markdown
Contributor

@LittleSaya LittleSaya commented Jun 21, 2019

…iaDB

Pull Request check-list

Please make sure to review and check all of these items:

  • Does npm run test or npm run test-DIALECT pass with this change (including linting)?
  • Does the description below contain a link to an 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)?
  • Did you follow the commit message conventions explained in CONTRIBUTING.md?

Description of change

The @returns part in the document of upsert is a little confusing. It actually returns true when inserted and returns false when updated, so I modified the doc to make it more clear.

Related issue: #7089

@sushantdhiman sushantdhiman merged commit 2bdcc5d into sequelize:master Jun 21, 2019
@sushantdhiman
Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 5.8.11 🎉

The release is available on:

Your semantic-release bot 📦🚀

@sushantdhiman
Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 7.0.0-next.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants