Commit ff9146ab authored by Vadim Zeitlin's avatar Vadim Zeitlin

Explicitly disable exact floating point comparison in SQLite test.

Exact comparisons were not done anyhow because they are currently disabled by
default, but make this more explicit because SQLite is known to fail them (and
seems to be unlikely to ever pass them).
parent 7039d009
......@@ -366,6 +366,24 @@ public:
return "datetime(\'" + datdt_string + "\')";
virtual bool has_fp_bug() const
SQLite seems to be buggy when using text conversion, e.g.:
% echo 'create table t(f real); \
insert into t(f) values(1.79999999999999982); \
select * from t;' | sqlite3
And there doesn't seem to be any way to avoid this rounding, so we
have no hope of getting back exactly what we write into it unless,
perhaps, we start using sqlite3_bind_double() in the backend code.
return true;
int main(int argc, char** argv)
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment