You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to the SQL standard, floating point values that aren't regular values should be considered errors. The engine shouldn't produce NaN or Infinity:
SQL> select asin(2), cot(0) from rdb$database;
ASIN COT
======================= =======================
NaN Infinity
SQL> select acos(2) - acos(2) from rdb$database;
SUBTRACT
=======================
NaN
We have two options: detect the problem once it has occurred (and give a generic message) or check the parameters. Since we know the functions we offer, the latter seems feasible.
ASIN, ACOS and COT should validate its argument, EXP should validate its result, LOG10 should check the input like LN does and POWER should validate its result.
Submitted by: Claudio Valderrama C. (robocop)
Assigned to: Claudio Valderrama C. (robocop)
Is related to QA404
According to the SQL standard, floating point values that aren't regular values should be considered errors. The engine shouldn't produce NaN or Infinity:
SQL> select asin(2), cot(0) from rdb$database;
======================= =======================
NaN Infinity
SQL> select acos(2) - acos(2) from rdb$database;
=======================
NaN
We have two options: detect the problem once it has occurred (and give a generic message) or check the parameters. Since we know the functions we offer, the latter seems feasible.
Commits: 4cd4c52 82d2c63
The text was updated successfully, but these errors were encountered: