Re: Undocummented: SET ISOLATION TO DIRTY READ

> SET ISOLATION TO REPEATABLE READ will lock each fetched row in thecursor. 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. 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? Thanks akent@cix.compulink.co.uk (Andy Kent) ------------------------------------- 44 272 742815