Such attributes can be later handled in client-side events. This property allows you to add simple metadata to individual elements, largely for the purpose of providing information to make JavaScript functions easier. For example, to set the font color and the background color for a control, place the following string to Inline styles: Use this field to set formatting options to be used inside the style attribute of the element. To limit end-user input to a specified range, turn ON the Use constraints option and define the editor's minimum and maximum allowed values. When an end-user presses a spin button, the value is incremented or decremented by this amount. Step specifies the legal number intervals for the input field. Can be specified in any units supported by web browsers e.g. Use this property to restrict the maximum width of the editor (this means that in any screen resolution editor's width will be less or equal then the property value). The editor consists of an edit region and one pairs of spin buttons which can be used to adjust the numerical value.

We can check whether the CHECK constraint is the one that LibreOffice puts when faking BOOLEAN.Select this control to create a single-line input field allowing users to edit numeric values with ease. > every time we read a SMALLINT (that's the smallest datatype in firebird. > However we could simply read whether there is a CHECK constraint in place in the UI when editing table data directly (because Base > when reading it won't present itself as a boolean, i.e. > as a boolean would also work fine, however there is still the issue that > then, the table has a TINYINT(1) field, not a BOOLEAN field.) > It shouldn't be that hard to fake it at creation time, and reading the field Could we fake BOOLEAN in the driver, if necessary? (Meaning, if (CHECK constraints (and not-nulls) are in RDB$CHECK_CONSTRAINTS, mapping to RDB$TRIGGERS, still need to figure out how to detect this specific check once there though.) However we could simply read whether there is a CHECK constraint in place every time we read a SMALLINT (that's the smallest datatype in firebird - there's no tinyint). in the UI when editing table data directly (because Base thinks it's just an integer). It shouldn't be that hard to fake it at creation time, and reading the field as a boolean would also work fine, however there is still the issue that when reading it won't present itself as a boolean, i.e.

> (note: firebird 3 has/will have BOOLEAN datatype) > then, the table has a TINYINT(1) field, not a BOOLEAN field.) > *creation* time, just map BOOLEAN to TINYINT(1) or something like that. Maybe we could just do it like MySQL and at table Could be it is a problem with the Bool-field inside of this table.

Firebird constraint limit