On Mon, Dec 22, 2003 at 05:41:27PM -0600, david nicol wrote: > A similar negative experience got me in the habit of being strict > with locking discipline when using DBM. > > open advisory file > lock advisory file (shared for reading, exclusive for writing) > tie data file > access data file > untie data file > unlock advisory file > close advisory file > > if you can queue up database activity, you can do more than one > in the "access data file" section; otherwise you need to do all > these steps to safely use a local hashed file.
David, Why the advisory file? I mean, why not lock the data file directly? Mx.
