[thelist] cflock reads?

[rudy]

> If a read is in progress and not locked, the write will lock
> the variable from *new* accesses ( not current reads), then
> proceed to write.  At that point, you have a simultaneous
> read and write and possibly corrupted memory.

thanks chris

that, finally, makes sense

i'd've thought, though, that an exclusive lock would not begin until any
other processes are done and outta there

live & learn, i guess


<tip type="sql" remarks="an oldie but a goodie">
Why SELECT * is bad
http://www.adopenstatic.com/faq/selectstarisbad.asp
</tip>

rudy