Outch! So if you drop and recreate the index, the problem should go away. If that's true, then it's a bug and the only work around is going to be a drop and recreate of the index. (Not good.)
This should also be a repeatable problem too. The issue isn't in the table but the index. Or am I missing something? -Mike > -----Original Message----- > From: jrgchip [mailto:[email protected]] > Sent: Friday, January 30, 2009 9:10 AM > To: [email protected] > Subject: Re: Record not found in some SQL - Bug? > > > > jrgchip wrote: > > > > The failure still occurs. > > > > Per investigation in DERBY-4032, it appears that there is indeed a bug in > Derby. The problem here is that there are two records for 'HG15497' in > the > unique index on the Product table (one active and one marked as deleted) > and > that the B-tree scan logic does not account for that possibility. So, > depending on the access path chosen and the logic used to satisfy the > query, > the record might be found or not found. > > -- > View this message in context: http://www.nabble.com/Record-not-found-in- > some-SQL---Bug--tp21700110p21748874.html > Sent from the Apache Derby Users mailing list archive at Nabble.com.
