Skip to content
This repository has been archived by the owner on Aug 21, 2023. It is now read-only.

sql: fix where condition without brackets problem #372

Merged
merged 2 commits into from
Oct 14, 2021

Conversation

lichunzhu
Copy link
Contributor

@lichunzhu lichunzhu commented Oct 14, 2021

What problem does this PR solve?

close #371

What is changed and how it works?

If both conf.Where and where has a value, we use brackets to wrap these two conditions.

Check List

Tests

  • Unit test
  • Integration test
    Dumpling before this commit can't pass new integration tests.

Side effects

  • Possible performance regression

Related changes

  • Need to cherry-pick to the release branch

Release note

  • fix the problem that dumpling may dump extra data if --where is specified

@ti-chi-bot
Copy link
Member

ti-chi-bot commented Oct 14, 2021

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • glorv

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

Copy link
Collaborator

@glorv glorv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rest LGTM

v4/export/sql.go Outdated Show resolved Hide resolved
@ti-chi-bot ti-chi-bot added the status/LGT1 One reviewer approved (LGTM1) label Oct 14, 2021
@@ -40,6 +40,27 @@ expected=$(seq 3 9)
echo "expected ${expected}, actual ${actual}"
[ "$actual" = "$expected" ]

# Test for OR WHERE case. **Must dump MySQL here!!**
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Must dump MySQL here!! What does this mean?🤔

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about change these words to:
Better dump MySQL here because Dumpling has some special handle for concurrently dump TiDB tables.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@lichunzhu
Copy link
Contributor Author

/merge

@ti-chi-bot
Copy link
Member

This pull request has been accepted and is ready to merge.

Commit hash: e6d5341

@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created: #373.

@lichunzhu lichunzhu deleted the fixWhereConditionProblem branch October 14, 2021 11:32
@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created: #374.

@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created: #375.

@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created: #376.

tisonkun pushed a commit to tisonkun/dumpling that referenced this pull request Oct 20, 2021
tisonkun pushed a commit to tisonkun/dumpling that referenced this pull request Oct 20, 2021
tisonkun pushed a commit to tisonkun/dumpling that referenced this pull request Oct 20, 2021
tisonkun pushed a commit to tisonkun/dumpling that referenced this pull request Oct 20, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

dumpling may dump extra data if --where is specified
5 participants