Skip to content
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

[opt](Nereids) adjust operator precedence #43632

Merged
merged 1 commit into from
Nov 12, 2024

Conversation

morrySnow
Copy link
Contributor

@morrySnow morrySnow commented Nov 11, 2024

Problem Summary:

adjust operator precedence to let it same with MySQL.

!
+ (unary plus), - (unary minus), ~ (unary bit inversion) ^
*, /, DIV, %
-, +
&
|
=(comparison), <=>, >, <=, <, <>, !=, IS, LIKE, REGEXP, MATCH, IN
NOT
AND, &&
XOR
OR, ||

Release note

Change operator precedence behavior. Let it same with MySQL.

None

Check List (For Author)

  • Test

    • Regression test
    • Unit Test
    • Manual test (add detailed scripts or steps below)
    • No need to test or manual test. Explain why:
      • This is a refactor/code format and no logic has been changed.
      • Previous test can cover this change.
      • No code files have been changed.
      • Other reason
  • Behavior changed:

    • No.
    • Yes.

Change operator precedence behavior. Let it same with MySQL.

  • Does this need documentation?
    • No.
    • Yes.

Check List (For Reviewer who merge this PR)

  • Confirm the release note
  • Confirm test cases
  • Confirm document
  • Add branch pick label

@doris-robot
Copy link

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@morrySnow
Copy link
Contributor Author

run buildall

!
+ (unary plus), - (unary minus), ~ (unary bit inversion)
^
*, /, DIV, %
-, +
&
|
=(comparison), <=>, >, <=, <, <>, !=, IS, LIKE, REGEXP, MATCH, IN
NOT
AND, &&
XOR
OR, ||
@morrySnow
Copy link
Contributor Author

run buildall

Copy link
Contributor

PR approved by at least one committer and no changes requested.

@github-actions github-actions bot added approved Indicates a PR has been approved by one committer. reviewed labels Nov 12, 2024
Copy link
Contributor

PR approved by anyone and no changes requested.

@morrySnow morrySnow merged commit f6b0f0a into apache:master Nov 12, 2024
26 of 28 checks passed
@morrySnow morrySnow deleted the operator_precedence branch November 12, 2024 12:00
py023 pushed a commit to py023/doris that referenced this pull request Nov 13, 2024
### Problem Summary:

adjust operator precedence to let it same with MySQL.

!
+ (unary plus), - (unary minus), ~ (unary bit inversion) ^
*, /, DIV, %
-, +
&
|
=(comparison), <=>, >, <=, <, <>, !=, IS, LIKE, REGEXP, MATCH, IN
NOT
AND, &&
XOR
OR, ||

### Release note

Change operator precedence behavior. Let it same with MySQL.
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.

4 participants