Improve the almost useless "expression evaluation not supported" message [CORE1799]

[firebird-automations]

Submitted by: Claudio Valderrama C. (robocop)

Assigned to: Claudio Valderrama C. (robocop)

Votes: 1

This "expression evaluation not supported" message makes me sick since IB4. In big stored procedures or complex queries it's almost impossible to know immediately what went wrong, since no more information is available.
This message has number 286 in the JRD facility and appears 46 times in the JRD directory (8 in cmp.cpp, 8 in evl.cpp and 30 times in SysFunction.cpp).
Also, the same text has number 167 in the SQLERR facility, although I can't find where it's used.

Either the same message should be given parameters (and old clients will ignore them) or new messages should be appended as subcodes. Currently, guessing here the offending code is really hard game.

Commits: 586c3a6 0c85fac

[firebird-automations]

Modified by: Claudio Valderrama C. (robocop)

issuetype: New Feature [ 2 ] => Improvement [ 4 ]

assignee: Claudio Valderrama C. [ robocop ]

[firebird-automations]

Modified by: Claudio Valderrama C. (robocop)

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

resolution: Fixed [ 1 ]

Fix Version: 2.5 Beta 1 [ 10251 ]

[firebird-automations]

Modified by: @pcisar

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

[firebird-automations]

Modified by: @pavel-zotov

QA Status: No test