Robert,

you are a genius in finding bugs :).

The bug has been reported by two users before you.
Since CHECK TABLE says ok, the table is probably
ok now.

The bug may be in purge in multiversioning: it removes
a secondary index record too early. Or it may the
in a lock wait.

Can you describe what operations could cause the
secondary index entry to change:

- Do you delete rows from USER_USER?
- Do you update the column containing 'Ambjorg'?
- Do you use REPLACE to update the column containing
  'Ambjorg'?

What is the create table statement for USER_USER?
What is the content of row number 7451 in the table
presently, or does it exist at all?

By the way, why there seem to be tuples for
'ambjorg', 'Ambjorg', and 'AMBJORG'?

Regards,

Heikki

>Er, a little embarassed that I did not check the bugfixes page before
>reporting that.  Anyhow, here is the check table to go with that report:
>
>+----------------------+-------+----------+----------+
>| Table                | Op    | Msg_type | Msg_text |
>+----------------------+-------+----------+----------+
>| rateGenius.USER_USER | check | status   | OK       |
>+----------------------+-------+----------+----------+
>
>robert
>
>-- 
>robert cope         \ Water?  No thank you, fish make love in it.
>[EMAIL PROTECTED] / 
>                    \ 
>
>



---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Reply via email to