Re: Repeatable read isolation level and locks

In article <34d9d545.45121431@client1.news.psi.net>, Jeff Larsen <larsen@qec.com> writes >I have two questions concerning repeatable read isolation level and >row locks. > >1. Why is a lock placed on the index value for the NEXT row > after the one I select? Is there anyway around this? > Probably because you have page level locking on the table. Try doing alter table <tablename> lock mode (row); >2. I want my application to query sysmaster:syslocks (is there > another way?) to inform the user that the row being viewed > can not be updated. What is the significance (in detail) of > the value of the keynum column and why is the type column null > for locks held by my application? > >I'm sorry, that was really more than two questions, but >answers (or pointers to references) to any of them will >be greatly appreciated. > >Thanks, > >Jeff -- David Williams Maintainer of the Informix FAQ Primary site (Beta Version) http://www.smooth1.demon.co.uk Official site http://www.iiug.org/techinfo/faq/faq_top.html I see you standin', Standin' on your own, It's such a lonely place for you, For you to be If you need a shoulder, Or if you need a friend, I'll be here standing, Until the bitter end... So don't chastise me Or think I, I mean you harm... All I ever wanted Was for you To know that I care