Config option to raise an SQL error on inserting a too long string value

Inserting of any string value should not result with a silent automatic truncation of a given value and with an OK transaction result status.
Exactly this is the default DBMS behaviour for non-ANSI databases.
One solution for this could be the introduction of a new configuration setting, eg. IFX_STRING_TOO_LONG_MODE.
Such a setting would enable administrators choosing between:
* 0: silent string truncation and SQL execution (current default)
* 1: raise an SQL error (like -1279: 'Value exceeds string column length.' for ANSI databases)

This string data truncation is even more unwanted behaviour for the users of multibyte charsets, e.g. UTF-8 in DB_LOCALE 'hr_hr.utf8'. That is related with the fact that declared length of a char fields is limiting the number of bytes (and not the number of characters) for the possible values. String validation can be easily done for the size (the number of characters), but the need for controlling the number of bytes used is not so obvious. As the number of bytes is variable and dependant on a number of multibyte characters used in a given value, it is possible (and likely) to overflow limited/declared number of bytes for a column.

The same logic applies for saving an encrypted text value, where DBMS is expected to save a given string value as a whole or raise an error. If a truncated value is saved, it leaves a user with an incomplete or even completely unusable data.