Locking without the indexes in a multiuser environment using INFORMIX SE Ver. 7.XX

Dear Art Kegal/Jonathan Lefler and all, We have the following problem. In INFORMIX -SE version 4.xx, 5.xx we were able to do the following on the stores7:customer table. First telnet session: begin work; update customer set fname='Test1' where lname='Sadler' Second telnet session: begin work; update customer set fname='Test2' where lname='Pauli That means row level locking is working without any problem in SE versions prior to 7.XX. But this is not possible with the SE versions 7.xx unless if we not creates an indexes on the fname column on the customer table i.e. without an index it is not possible to update records this way.it locks the entire table in SE without an index. Practically it is not possible to create unique or composite indexes everytime we want to update records this way in a multi user environment. This is more complicated when you have composite key spanning several columns. We want to know whether this a known bug in the new versions of informix products( this is the same behaviour with IDS 7.xx) or the normal behaviour??. Is their a work around to resolve this in SE?? Please send us a solution ASAP. Kind Regards, K. P. __________________________________________________ Do You Yahoo!? Send instant messages with Yahoo! Messenger. http://im.yahoo.com/

In article <8ipj4d$q9v$1@news.xmission.com>, M G <h_e_l_p_99@yahoo.com> wrote: > I don't Know INFORMIX-SE but whith IDS 7.x when optimizer choose a sequential scan for a table, OnLine need read all rows in table although a row not match in the WHERE clause. so when a row is locked by other user, informix return an error such "cannot FETCH next row...". An index avoid this problem. > Dear Art Kegal/Jonathan Lefler and all, > > We have the following problem. > > In INFORMIX -SE version 4.xx, 5.xx we were able to do > the following on the stores7:customer table. > > First telnet session: > begin work; > update customer set fname='Test1' > where lname='Sadler'> > Second telnet session: > begin work; > update customer set fname='Test2' > where lname='Pauli> > That means row level locking is working without any > problem in SE versions prior to 7.XX. > But this is not possible with the SE versions 7.xx > unless if we not creates an indexes on the fname > column on the > customer table i.e. without an index it is not > possible to update records this way.it locks the > entire table in SE without an index. > Practically it is not possible to create unique or > composite indexes everytime we want to update records > this way in a multi user environment. This is more > complicated when you have composite key spanning > several columns. > We want to know whether this a known bug in the new > versions of informix products( this is the same > behaviour with IDS 7.xx) or the normal behaviour??. > Is their a work around to resolve this in SE?? > Please send us a solution ASAP. > > Kind Regards, > K. P. > > __________________________________________________ > Do You Yahoo!? > Send instant messages with Yahoo! Messenger. > http://im.yahoo.com/ > Sent via Deja.com http://www.deja.com/ Before you buy.