> ** The lock byte is obtained at > ** random so two separate readers can probably access the file at the > ** same time, unless they are unlucky and choose the same lock byte. > "can probably access the file at the same time" is better than "can't" > access, but there is no > guarantee. > Does commets like those mean that SQLite will work very often, but there are > known bugs not > resolved because thay are unlikely to appear, or problems like race > conditions are guarented to > be found is some other functions?
I'm not 100% sure what you're trying to do, but in the specific case of SHARED_LOCK, I think in the rare case if 2 readers happen to pick the same lock byte at random, one reader will simply block until the other is done with it. It's certainly not a potential bug even if the same lock byte is chosen, it would just slow it down by forcing access to be serialized. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
