-
-
Notifications
You must be signed in to change notification settings - Fork 246
Open
Labels
affect-version: 1.0.3affect-version: 1.5.4affect-version: 1.5.5affect-version: 2.0.0affect-version: 2.0.1affect-version: 2.0.2affect-version: 2.0.3affect-version: 2.0.4affect-version: 2.1 Alpha 1affect-version: 2.1 Beta 1affect-version: 2.1 Beta 2affect-version: 2.1 RC1affect-version: 2.1 RC2affect-version: 2.1.0affect-version: 2.5 Initialcomponent: enginepriority: majortype: improvement
Description
Submitted by: Claudio Valderrama C. (robocop)
It would be better if the logical, non-critical UDF errors are handled with a common, primary code. Example:
UDF error... deallocation error
UDF error... conversion error
UDF error... unknown data type (data type not supported).
Also, it's not clear why "data type is not supported" is treated as critical with IBERROR(169). This means currently a bugcheck, but if the UDF produced an unknown data type, it didn't damage the server neither the database. A bugcheck prevents the subsequent operation of the db, whereas a normal error allows to continue working with the db despite a logical mistake in the UDF.
Metadata
Metadata
Assignees
Labels
affect-version: 1.0.3affect-version: 1.5.4affect-version: 1.5.5affect-version: 2.0.0affect-version: 2.0.1affect-version: 2.0.2affect-version: 2.0.3affect-version: 2.0.4affect-version: 2.1 Alpha 1affect-version: 2.1 Beta 1affect-version: 2.1 Beta 2affect-version: 2.1 RC1affect-version: 2.1 RC2affect-version: 2.1.0affect-version: 2.5 Initialcomponent: enginepriority: majortype: improvement