Oninit® SQLMorph — Run-time Behaviour
| Topic | Behaviour |
|---|---|
| NULL | An expression with a NULL operand is NULL. Comparisons are three-valued; IF, WHILE and CASE take the false branch on unknown. Every routine is created WITH (HANDLESNULLS) so the function sees NULL arguments. |
| DECIMAL | Exact to 32 significant digits, overflow is an error, not a wrap. A result with no fixed scale is returned as DECIMAL(32). |
| CHAR | Blank-padded on assignment and comparison. |
| Integer range | Values outside the type’s range raise an error; the Informix NULL bit patterns are respected. |
| Array subscripts | Checked on every access. |
| status / sqlca | Set by every SQL statement. |
| Errors | Raised as engine exceptions unless WHENEVER ERROR says otherwise. |
| Interrupts | Loops yield to the engine and stop when the session is killed or the statement is cancelled. |
| Depth | At most 10,000 nested calls. |
| Memory | Strings, records and arrays are allocated from the engine’s memory and released on every way out of a function. |
| Time | TODAY and CURRENT use the server’s clock and time zone. |
A short list of behaviours comes from the Informix manuals and has not been compared against a 4GL compiler yet: the exact error numbers for some runtime errors, the initial value of a DATETIME variable, the treatment of a NULL in string concatenation, and the pivot for two-digit years. If you find a difference, the report page takes the 4GL and the result you expected.