Closed hakimio closed 1 month ago
@hakimio when ieee754compatible
is disabled @cap-js/sqlite
and @cap-js/postgres
won't apply the IEEE754
output converters and therefor the results won't be IEEE754
compliant. This should be the case as long as you use odata_new_adapter
as the old adapter would post process all the results. When odata_new_adapter
is set it automatically turns on ieee754compatible
to make sure that the results match up, but if you actively disable the feature flag it should output non compliant results.
@BobdenOs ieee754compatible
setting works correctly with odata_new_adapter
as long as sql_simple_queries
is not enabled. The issue is with sql_simple_queries
not odata_new_adapter
.
Test cases:
✔ odata_new_adapter: false
+ sql_simple_queries: 1
+ ieee754compatible: false
✔ odata_new_adapter: true
+ sql_simple_queries: 0
+ ieee754compatible: false
❌ odata_new_adapter: true
+ sql_simple_queries: 1
+ ieee754compatible: false
The last case inconsistently outputs numbers as strings.
@BobdenOs
if you actively disable the feature flag it should output non compliant results
It doesn't as explained above.
Description of erroneous behaviour
Combination of
sql_simple_queries
andodata_new_adapter
features breaks"ieee754compatible": false
setting.Detailed steps to reproduce
_Also, reproducable with
"sql_simple_queries": 2
_$select
,$filter
,$apply
or pagination parameters.ieee754compatible
setting is ignored anddecimal
/int64
values are returned as stringsDetails about your project