mutate: { set{ _:42608 <test> "37.79697544"^^<xs:float> . # } } query: { query(func: has(test))@filter(eq(test,37.79697544)){ test } } respones: "data": { "query": [ { "test": 37.796975 } ] }, 37.796975 != 37.79697544 if you use 37.79697…

Some problems about float types

enzotar January 16, 2020, 6:36pm 7

Running into the same issue when storing Latitude/Longitude as a float. Chops off last digits, which would put you in a completely different location.

Topic		Replies	Views
Float values got cropped Dgraph	0	375	September 21, 2021
Extend number precision in answer Dgraph kind:question , dgraph	0	155	April 18, 2024
Do strings get converted to Float for inequality when the schema type is Float? Dgraph	1	336	August 10, 2020
Working with large floats Dgraph	1	126	June 22, 2024
Data type for money Users	5	712	September 11, 2019

Some problems about float types

Related topics