Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Soft locks and table buffering
Message
From
18/09/2002 15:18:38
 
 
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Miscellaneous
Thread ID:
00700960
Message ID:
00701991
Views:
17
That bring out some other concerns:
  • What do you do if the person that started the modification goes to lunch while his record is still not saved?
  • What if the application need to be accessed by the web?
  • If you move the database to SQL Server (or another DB), you will have to implement your own pessimist locking rule, since you cannot lock a record in SQL Server (AFAIK).

    I guess the only good answer will be given by the business rule of the client.

    >How exactly do you "deal with contention issues"? If two people are allowed to edit the same record, and they both make a bunch of changes, what's the fair way of deciding who gets to keep theirs? Seems easier to me to just not allow a person to edit while someone else is... Unless I'm missing something?
  • Previous
    Next
    Reply
    Map
    View

    Click here to load this message in the networking platform