about the (bad) twin problem solution

Hi, We are in big trouble caused by the informix solution to the twin problem. We have a very important table in our application with one unique index (for the primary key) and some non-unique indexes. There are lots of processes that insert rows into that table. Since the key values always grow (serial column), there's no reason to the twin problem to become a problem to us. What really happens is that when some process inserts a value, say X, in an indexed column with immediately lower value Y, no other process can insert a row with a value on this column between Y and X, until the first one finishes its transaction. This represents a big bottle-neck to us, since we have very long transactions. Since there's no reason to deal with non-unique indexes as with unique ones, in the resolution of the twin problem, I think this is a known bug since Informix-Turbo and I'd expect it to be solved at least on OnLine 5.0, but it is not. So, if anyone knows some workaround for this 'twin' problem, please let me know. Informix, when will this bug be fixed? BTW: I've found this problem in two configurations INFORMIX-SQL 4.10.UD1 - Online 4.10.UE1 DB-Access 5.00.UC2 - Online 5.00.UC2 both under ULTRIX 4.2 in a DECstation 3100 Thanks. ------------------------------------------------------------------------------- | Manuel Figueiredo Monteiro | | S.S.F. - Servicos de Software Financeiro, Lda VOICE: +351 (1) 727-0303 | | Estrada da Luz, No 104 - Loja A FAX: +351 (1) 727-0335 | | 1600 Lisboa E-MAIL: mm@ssf.pt | | PORTUGAL | -------------------------------------------------------------------------------