KLW

Results 8 comments of KLW

The execution results of the NOT operator are inconsistent between DOUBLE type data and INTEGER UNSIGNED type data.

Thanks for fixing this! Good Job!

Abnormality in binary arithmetic operations involving the time field.

Thank you for your reply. 😊😊😊

In version 5.7.0 of GridDB, GroupByRange fails to retrieve values as expected.

![In version 5 7 0 of GridDB, GroupByRange fails to retrieve values as expected](https://github.com/user-attachments/assets/64b5314d-2211-41f2-81a7-2dd6aea34c1b)

In version 5.7.0 of GridDB, GroupByRange fails to retrieve values as expected.

Thank you for the clarification! I fully understand the design considerations regarding the grouping limit and will adjust the SQL query conditions as suggested. I truly appreciate your team's initiative...

In version 5.7.0 of GridDB, When I combine the NOT and BETWEEN operators, the query unexpectedly retrieves additional null values.

![In version 5 7 0 of GridDB, When I combine the NOT and BETWEEN operators, the query unexpectedly retrieves additional null values](https://github.com/user-attachments/assets/6fb81d6b-5017-4bea-8b64-1a7cf6100ad1)

In version 5.7.0 of GridDB, When I combine the NOT and BETWEEN operators, the query unexpectedly retrieves additional null values.

Thank you for your thorough reply, which gave me a clear idea of the internal logic of the SQL implementation in question. 👍👍

In version 5.7.0 of GridDB, In time window aggregation, COUNT did not return the expected value of 0.

![In version 5 7 0 of GridDB, In time window aggregation, COUNT did not return the expected value of 0](https://github.com/user-attachments/assets/85773c83-25d1-4403-8b1f-57a232a88e1e)

Unexpected behavior in MetricsQL query with `!=` and `<=` operator comparison

Thank you for your response. I understand your point, and I appreciate the clarification that the behavior might be by design. However, I have carefully reviewed the official documentation of...