Record locking

[Jay R. Ashworth]

On Wed, Mar 31, 2004 at 12:15:30PM -0500, John Esak wrote:
> I understand what you are saying... and it probably _does_ have to do with
> Windows somewhere somehow... but filePro is working with in-memory values...
> not those written to disk... so if you say:
> 
>       num=ctl(1) and then refer to it later... filePro is using its own copy
> in memory of that value... it doesn't matter _when_ it gets written to
> disk... it is going to be written in the proper sequential order of
> things... or at least that is the way it is supposed to work... :-)

Unless two workstations both go after a copy at the same time.

If the code is written wrong, it's possible for them to both get the
same number; race conditions are a bitch.

Cheers,
-- jra
-- 
Jay R. Ashworth                                                jra at baylink.com
Member of the Technical Staff     Baylink                             RFC 2100
The Suncoast Freenet         The Things I Think
Tampa Bay, Florida        http://baylink.pitas.com             +1 727 647 1274

        "They had engineers in my day, too."  -- Perry Vance Nelson