The log(base, number) built-in function doesn't check parameters and delivers NAN values instead. [CORE1936]

[firebird-automations]

Submitted by: Claudio Valderrama C. (robocop)

Is related to QA348

Unlike ln(number), the log(base, number) function doesn't check its parameters. Examples of what happens with illegal params follow:

SQL> select log(2, 00) from rdb$database;

                LOG

=======================
-1.#⁠INF00000000000

SQL> select log(2, -2) from rdb$database;

                LOG

=======================
-1.#⁠IND00000000000

SQL> select log(0, 1) from rdb$database;

                LOG

=======================
-0.0000000000000000

SQL> select log(0, 2) from rdb$database;

                LOG

=======================
-0.0000000000000000

SQL> select log(-1, 2) from rdb$database;

                LOG

=======================
-1.#⁠IND00000000000

SQL> select log(-1, 0) from rdb$database;

                LOG

=======================
-1.#⁠IND00000000000

SQL> select log(-1, -1) from rdb$database;

                LOG

=======================
-1.#⁠IND00000000000

Commits: 142f989

[firebird-automations]

Modified by: @asfernandes

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.5 Beta 1 [ 10251 ]

assignee: Adriano dos Santos Fernandes [ asfernandes ]

[firebird-automations]

Modified by: @pcisar

Link: This issue is related to QA348 [ QA348 ]

[firebird-automations]

Commented by: @pcisar

QA test added.

[firebird-automations]

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

[firebird-automations]

Modified by: @pavel-zotov

QA Status: No test

[firebird-automations]

Modified by: @pavel-zotov

QA Status: No test => Done successfully