SQL:
Attributes


ADMIN

If true, the sql command will be ran through the administrator connection, which is set up using the configuration options db_username_admin and db_username_password; the normal host and database are used.

If the replication is enabled, it will use the remote admin connection.

Value(s)

Default Value

false

DISALLOWCORRECTION

Where False this gives the user a chance to re-edit the form and try again if the database refuses their commit.

Value(s)

Default Value

true

DYNAMIC_TABLE_NAMES

It is possible to have dynamically selected table names in a dbobject, i.e. using a widget/field element to determine the table name during run time. However, this does add a certain amount of overhead to the application, so should only be enabled on dbobjects that require this feature. The default is disabled.

Value(s)

Default Value

false

PURIFY

By default, values retrieved from or tags will be made SQL safe (purified). If purify is set to false, this will be disabled, which can be desirable in certain circumstances. Generally speaking, it's safer to leave this enabled. Note that this may also be specified on a per widget/field basis; if it is necessary to disable the purification, then it's safest so disable only the widgets for which it is required.

Value(s)

Default Value

true

UPDATE

write the result into the named widget(s) expects a single name or multiple names spearated by spaces (ascii 32)

Value(s)

CDATA

Default Value

#IMPLIED

UPDATECONTAINER

If the containing DTD element should be updated with the result of the SQL when it is executed. This is mainly used for widgets with sql embedded in their values, where the container is not explicitly named. For example

<label><sql>SELECT 'foo';</sql></label>

Value(s)

Default Value

false

VERBOSE

Controls whether SQL error messages should be reported.

Value(s)

Default Value

true

WRITEACTION

Indicates that the sql may cause writes to the database - useful where database replication is in use replication.

Value(s)

Default Value

false
Back to SQL


bond-2.1 DTD