William,

As I mentioned earlier (item 06 below), ROWLOCKing 
is used when working with a Form or in a BROWSE/EDIT 
mode-just a single row of data is modified at a time.

With QUALCOLS 10 (default), automatic page locking is 
used with the UPDATE and DELETE commands, and the 
INSERT command using a SELECT clause - many rows of 
data can be affected by one command.

With automatic page locking (QUALCOLS 10), R:BASE 
locks a page of data (8,192 bytes), reads the page, 
performs the operation, then releases the lock. By 
locking a page of data at a time instead of a row 
data at a time, fewer locks are required and there 
is less chance of a conflict between workstations 
when performing UPDATES or DELETES on large number 
of rows.

With automatic row locking (ROWLOCKS ON), R:BASE 
locks a row of data, reads the row, performs the 
operation and then releases the lock. 

When QUALCOLS is SET to 2 (QUALCOLS 2), i.e, row 
locking only, there is no page locking and R:BASE 
locks a row, reads the row, make the changes and 
then releases the row.

Hope that helps to understand. 

Have a GREAT Weekend! 

Very Best Regards, 

Razzak. 



At 01:53 PM 10/5/2001 -0700, William Mason wrote:
>Dr R>
>
>Could you please explain the relationship 
>(or lack thereof) between ROWLOCKS and the 
>QUALCOLS setting?
>
>Sorry to be dense...
>
>wm
>
>----- Original Message -----
>From: "A. Razzak Memon" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Sent: Friday, October 05, 2001 12:14 PM
>Subject: Re: ROWLOCKS vs FASTLOCK - Razzak's Reply
>
>
>>
>> At 10:28 AM 10/5/2001 -0700, Bernie Corrigan wrote:
>>
>> >Can someone tell me the functional difference between
>> >ROWLOCKS and FASTLOCK?
>>
>> Bernie,
>>
>> Here you go ...
>>
>> 01. ROWLOCKS (Default: ON)
>>     FASTLOCK (Default: OFF
>>
>> 02. ROWLOCKS only locks the required row for the current
>>     command instead of locking the entire table.
>>
>>     FASTLOCK, when ON, speeds Multi-User performance while
>>     modifying data and does not place lock on the table,
>>     allowing for greater throughput.
>>
>> 03. ROWLOCKS ON does not require STATICDB ON
>>
>>     FASTLOCK ON requires STATICDB ON.
>>
>> 04. ROWLOCKS can be turned ON or OFF after CONNecting the
>>     database.
>>
>>     FASTLOCK can only be turned ON before STATICDB is set
>>     to ON and CONNecting the database.
>>
>>     Typical Example:
>>
>>     SET STATICDB ON
>>     SET FASTLOCK ON
>>     CONNECT Database
>>
>> 05. In a Multi-User environment, ROWLOCKS can be SET to
>>     ON or OFF by individual user(s).
>>
>>     In a Multi-User environment, 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, similar to STATICDB,
>>     MULTI and TRANSACT.
>>
>>     Having the STATICDB ON, FASTLOCK ON and QUALCOLS 2 is
>>     the fastest method for updating data in a Multi-User
>>     environment.
>>
>> 06. ROWLOCKing is used when working with a Form or in a
>>     BROWSE/EDIT mode - just a single row of data is
>>     modified at a time.
>>
>>     Commands such as UPDATE, INSERT and DELETE perform
>>     much faster with FASTLOCK set to ON.
>>
>> There you have it ...
>>
>> Very Best Regards,
>>
>> Razzak.
>>
>>
>> ===================================-============================
>> R:BASE Developers's Conference: http://www.rbase.com/conference
>> Official R:BASE List Server:    mailto:[EMAIL PROTECTED]
>> RBTI Events/Training:      http://www.rbase2000.com/events
>> R:DCC Members:      http://www.rbase2000.com/rdcc
>> ================================================================
>> R:BASE, Oterro & R:Tango are registered trademarks of RBTI.
>> ==================================-=============================
>>
>>
>
>

Reply via email to