Meaningless Drivel is fun!* The moose likes Developer
Certification (SCJD/OCMJD) and the fly likes NX (contractors):
find() and dirty reads Big Moose Saloon Register / Login
Bookmark "NX (contractors): find() and dirty reads" Watch "NX
(contractors): find() and dirty reads" New topic  NX
(contractors): find() and dirty reads  Rob Zidsen  Joined: Jul
07, 2003 Posts: 16 To prevent dirty reads and such, would you
guys recommend locking the whole database when performing
find()? This would prevent one thread from changing a record in
the middle of another thread searching through the whole
database to find matching records. On the other hand, this may
cause clients to appear to hang if there are too many calls to
find() and the database is large. Jim Yingst  Joined: Jan 30,
2000 Posts: 18671 Well, speaking as someone who routinely
complains about the possibility of dirty reads elsewhere - I
think that the find() method is the place where dirty reads are
most acceptable. The find() method is probably the slowest,