dbTalk Databases Forums  

D3/NT 7.5 FSI Record Locking

comp.databases.pick comp.databases.pick


Discuss D3/NT 7.5 FSI Record Locking in the comp.databases.pick forum.



Reply
 
Thread Tools Display Modes
  #21  
Old   
Mike Preece
 
Posts: n/a

Default Re: D3/NT 7.5 FSI Record Locking - 08-12-2006 , 01:19 AM







Maybe I could express this better...

The problem as stated was that both/multiple threads could see the lock
as available and both attempt to take ownership, with the first attempt
being overwritten/overridden by subsequent attempts. By *appending* to
a lock *array*, rather than a scalar value, we remove the possibility
of anything being overwritten. Only the first element in the array has
any significance. Any clearer?

Mike.


Reply With Quote
  #22  
Old   
murthi
 
Posts: n/a

Default Re: D3/NT 7.5 FSI Record Locking - 08-12-2006 , 01:57 PM






I think you're right about not having to test for the null. If you don't
test for null, B will think he failed, will stall and try again (though he
does not have to). So it works...ok...good.

Chandru

"Mike Preece" <michael (AT) preece (DOT) net> wrote

Quote:
Maybe I could express this better...

The problem as stated was that both/multiple threads could see the lock
as available and both attempt to take ownership, with the first attempt
being overwritten/overridden by subsequent attempts. By *appending* to
a lock *array*, rather than a scalar value, we remove the possibility
of anything being overwritten. Only the first element in the array has
any significance. Any clearer?

Mike.




Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.