Details
-
Epic
-
Resolution: Unresolved
-
Major
-
5.0.0
-
None
Description
explain select 77777772222222222.01; |
"#operator": "InitialProject", |
"result_terms": [ |
{
|
"expr": "77777772222222224" |
}
|
]
|
}
|
The expression value is wrong. This is just show. But there is bigger problem. Due to floating point precision the value will change but that needs to be consistent across the couchbase. For
example you save document in KV using UI {"k0":77777772222222222.01} will show as {"k0":77777772222222220}
When you do select * from default; it shows as {"k0":77777772222222224}
But in 4.5.0 it shows right.
Rreported by Prathibha Bisarahalli
Attachments
Issue Links
- is duplicated by
-
MB-61365 Inserts via transactions of large numbers truncated in 7.6.0
- Reopened
-
MB-29391 [INT64] Modulo operation returns incorrect result only in case of int64
- Closed
- is parent task of
-
MB-20395 select a long value which is < maxint64 also shows values > maxint64
- Open
- relates to
-
MB-31798 Values greater than MaxFloat64 get evaluated as Binary type
- Closed
-
MB-20395 select a long value which is < maxint64 also shows values > maxint64
- Open
-
MB-29391 [INT64] Modulo operation returns incorrect result only in case of int64
- Closed
-
MB-29393 Incorrect results returned in case of scan for min int64 value
- Closed
-
MB-29401 sum of large negative numbers gives wrong results
- Closed
-
MB-20354 big integer: SELECT MININT returns wrong answer
- Closed
1.
|
select a long value which is < maxint64 also shows values > maxint64 | Open | Unassigned |