Re: Undocummented: SET ISOLATION TO DIRTY READ

Andy Kent (akent@cix.compulink.co.uk) wrote: : > SET ISOLATION TO REPEATABLE READ will lock each fetched row in the : cursor. : In some versions the lock testing/ acquisition is done on every row : *touched* rather than every row fetched. So non-indexes searches can be : mighty expensive with Repeatable Read. Haven't seen this, which versions? : Can anyone tell me which version this is changed in? : Also, I think I've sometimes seen OnLine (4.10) just not bother to lock : the rows but lock the table instead. Can anyone confirm/ deny this and if : it's true, under what circumstances does it occur? Also have not seen this, I would like to know, as it would be a disaster in numerous systems I have designed! -- @ David Tomlinson @ @ dtomlnsn@netcom.com @ @ "I want my own monster! Get me a monster now!" @