RE: A BUG in IDS7.3UC2

We have almost the same problems as yours, we call it "composite index" problem. Here is what we did, 1. select from a normal table into temp table1 2. create a composite index on the temp table1 3. select from temp table1 into temp table2 w/o composite index, we can get the right no of row, w index, only 0 or 1 returned. We use informix 7.30.uc2 on sun solaris 2.5.1/2.6. On 7.23.uc2 no problem. Informix tech support login and tested it, they repeated the errors on our system. But unfortunately, they couldn't repeat it on their system, so they can't tell if this is a bug on 7.3, but they are still working on that. julia In article <70eotp$dd4$1@news.xmission.com>, Pazicky Ludovit <Ludovit.Pazicky@swh.sk> wrote: > > After playing a while I experienced following: > > 1. When I ran the script as it was I became the same results as Octav > 2. When I dropped the index and re-created it, the query returned the > correct result set > 3. Then I tried to drop the index, re-create it, updated the row to the > original state, updated as in script - correct result set > 4. Last experiment was drop the index, update the row to the original > state, re-create index, update as in script - wrong result set. > > It looks as the index does not work properly after update. > > Pazi > > (For remind IDS7.30-UC2, ReliantUNIX 5.44) > > -----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own