Skip to content

fix comparison result depends on operand order (#10888) - #10942

Open
dritter-sap wants to merge 3 commits into
developfrom
fix/10888-comparison-operand-order
Open

dritter-sap wants to merge 3 commits into
developfrom
fix/10888-comparison-operand-order

Conversation

@dritter-sap

Copy link
Copy Markdown
Collaborator

Fixes #10888.

@dritter-sap
dritter-sap requested a review from tglman October 15, 2026 21:07

@tglman tglman left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This looks good for now, I'm not 100% convinced by this, in the long term there was the plano of "normalization of conditions" so in practice flip condition "a" = field to field = "a" this would help for index lookups and also this cases, for now we could merge this, but then it will become redundant as normalization is done


// regression: #10888
@Test
public void test_issue10888_operandOrderSymmetry() {

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Naming do not respect java convention

// regression: #10888
@Test
public void test_issue10888_operandOrderSymmetry() {
db.command("CREATE CLASS D10888").close();

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Better class names

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

Labels

None yet

Development

Successfully merging this pull request may close these issues.

Comparison result depends on operand order: '2024-01-01 12:34:56' = d is false where d = '2024-01-01 12:34:56' is true

2 participants