Please enable JavaScript to view this site.

R:BASE 11 Help

Navigation: Reference Index > Environment Optimization

FASTLOCK

Scroll Prev Top Next More

One of the areas of most contention when updating or deleting data is the table lock that must be placed so that R:BASE knows the table is in use and the table structure cannot be modified. Each user modifying data places this lock, and uses the same lock location. With STATICDB set ON, no structure changes are possible on permanent database tables, thus, there is no need for a table lock preventing a user from modifying the structure of a table. Since the lock is not needed, the FASTLOCK setting was added in R:BASE to allow users to turn this table lock off. Commands such as UPDATE, INSERT and DELETE perform much faster with FASTLOCK ON.

 

The FASTLOCK setting must match for all users of a database and must be set before a database is connected. Users cannot connect a database unless their FASTLOCK setting matches the setting of the open database. FASTLOCK joins STATICDB, MULTI, and TRANSACT as settings that must match for all users connected to a database. FASTLOCK cannot be set ON unless STATICDB is ON. If you SET FASTLOCK ON and connect the database, but STATICDB is OFF, after connecting to the database FASTLOCK is set OFF.