MAX_INT / 1 results in overflow

[DominicWuest]

I found a discrepancy when running two semantically equivalent queries against an empty database:

---

1:

RETURN 9223372036854775807

Produces:

9223372036854775807

---

2:

RETURN 9223372036854775807 / 1

Produces:

-9223372036854775808

---

I believe the queries mentioned above are semantically equivalent and thus their result should be the same.

Also, I think it may be unexpected behaviour to have an overflow when dividing MAX_INT by 1.

I encountered this issue when testing queries on the FalkorDB master branch in a Docker container running redis:7.2.3-bookworm.

Steps to reproduce

Run the aforementioned, semantically equivalent, queries against an empty database and observe that their results differ.

Expected behavior

The queries should result in the same behavior

Actual behavior

The query results differ

[swilly22]

Hi @DominicWuest,

Thank you for brining this to our attention, to be honest I'm not if this issue will get priority as int64 overflows are quite rare to encounter and the overhead of checking for an overflow on each operation might not be worth it.

I'm going to leave this issue open for the time being.