General information
Category:
Databases,Tables, Views, Indexing and SQL syntax
SNIP
>From a "best practices" POV, are you better to :-
>
>A) LOCK all candidate records first and THEN process all of the locked records.
>
>or...
>
>B) Buffer the table and individually lock/process each candidate record in sequence (or abort the whole job when a record lock cannot be achieved) and depending on a success flag, TableUpdate() or TableRevert() the buffered data.
>
>I am taking about a "free table" updated from a processing program. There is no View involved and this operation is running in a SESSION CLASS subclass.
>
>Any advice would be very much appreciated.
I just want to remind you that RLOCK() can handle multiple records. That might make it a bit easier or give you more confidence.
good luck
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only