Application: gvSIG desktop

		<field name="port" type="integer" mandatory="false" defaultValue="9123" group="Connection">

        <!--

        <field name="LOCK_TIMEOUT" type="integer" mandatory="false" group="Advanced" defaultValue="1000" >

          <description>Sets the lock timeout (in milliseconds) for the current session. The default value for this setting is 1000 (one second).</description>

        </field>

        <field name="MULTI_THREADED" type="integer" mandatory="false" group="Advanced" defaultValue="1000" >

          <description>Enabled (1) or disabled (0) multi-threading inside the database engine. MULTI_THREADED is enabled by default with default MVStore storage engine. MULTI_THREADED is disabled by default when using PageStore storage engine, enabling this with PageStore is experimental only.

This is a global setting, which means it is not possible to open multiple databases with different modes at the same time in the same virtual machine. This setting is not persistent, however the value is kept until the virtual machine exits or it is changed.

Admin rights are required to execute this command, as it affects all connections</description>

        </field>

        <field name="CHACHE_SIZE" type="integer" mandatory="false" group="Advanced" defaultValue="-1" >

          <description>Sets the size of the cache in KB (each KB being 1024 bytes) for the current database. The default is 65536 per available GB of RAM, i.e. 64 MB per GB. The value is rounded to the next higher power of two. Depending on the virtual machine, the actual memory required may be higher.

This setting is persistent and affects all connections as there is only one cache per database. Using a very small value (specially 0) will reduce performance a lot. This setting only affects the database engine (the server in a client/server environment; in embedded mode, the database engine is in the same process as the application). It has no effect for in-memory databases.

Admin rights are required to execute this command, as it affects all connections. This command commits an open transaction in this connection. This setting is persistent.?

If -1 use the default value.</description>

        </field>

        <field name="LOG" type="integer" mandatory="false" group="Advanced" defaultValue="2" >

          <availableValues>

            <value label="0 - Transaction log is disabled completely">0</value>

            <value label="1 - Transaction log is enabled, but FileDescriptor.sync is disabled">1</value>

            <value label="2 - Transaction log is enabled, and FileDescriptor.sync is called for each checkpoint">2</value>

          </availableValues>

          <description>Sets the transaction log mode. The values 0, 1, and 2 are supported, the default is 2. This setting affects all connections.

LOG 0 means the transaction log is disabled completely. It is the fastest mode, but also the most dangerous: if the process is killed while the database is open in this mode, the data might be lost. It must only be used if this is not a problem, for example when initially loading a database, or when running tests.

LOG 1 means the transaction log is enabled, but FileDescriptor.sync is disabled. This setting is about half as fast as with LOG 0. This setting is useful if no protection against power failure is required, but the data must be protected against killing the process.

LOG 2 (the default) means the transaction log is enabled, and FileDescriptor.sync is called for each checkpoint. This setting is about half as fast as LOG 1. Depending on the file system, this will also protect against power failure in the majority if cases.

Admin rights are required to execute this command, as it affects all connections</description>

        <field name="LOCK_MODE" type="integer" mandatory="false" group="Advanced" defaultValue="3" >

          <availableValues>

            <value label="0 - READ_UNCOMMITTED, no locking">0</value>

            <value label="1 - SERIALIZABLE, table level locking">1</value>

            <value label="2 - Table level locking with garbage collection">2</value>

            <value label="3 - READ_COMMITTED, table level locking+read locks released immediately">3</value>

          </availableValues>

          <description>Sets the lock mode. The values 0, 1, 2, and 3 are supported. The default is 3 (READ_COMMITTED). This setting affects all connections.

The value 0 means no locking (should only be used for testing; also known as READ_UNCOMMITTED). Please note that using SET LOCK_MODE 0 while at the same time using multiple connections may result in inconsistent transactions.

The value 1 means table level locking (also known as SERIALIZABLE).

The value 2 means table level locking with garbage collection (if the application does not close all connections).

The value 3 means table level locking, but read locks are released immediately (default; also known as READ_COMMITTED).

</description>

        </field>

        -->