These are the warnings:
Table w_users - check - warning -
Found row where the auto_increment column has the ...Problems with indexes of table `w_blocks`
UNIQUE and INDEX keys should not both be set for column `theme`Problems with indexes of table `w_filters`
UNIQUE and INDEX keys should not both be set for column `format`Problems with indexes of table `w_menu_links`
More than one INDEX key was created for column `menu_name`Problems with indexes of table `w_node`
PRIMARY and INDEX keys should not both be set for column `nid`Problems with indexes of table `w_search_index`
UNIQUE and INDEX keys should not both be set for column `word`Problems with indexes of table `w_system`
More than one INDEX key was created for column `type`Problems with indexes of table `w_term_data`
More than one INDEX key was created for column `vid`Problems with indexes of table `w_term_hierarchy`
PRIMARY and INDEX keys should not both be set for column `tid`Problems with indexes of table `w_votingapi_cache`
More than one INDEX key was created for column `content_type`Problems with indexes of table `w_votingapi_vote`
More than one INDEX key was created for column `content_type`
I think it is indeed not sensible to create more than one index for one table column. Or is there something behind it that the checker and I don't understand?
Comments
Comment #1
Sunshiney commentedI am getting these warnings, also, via phpmyadmin. I'm not knowledgeable about mysql. Are we suppose to fix these warnings? How? No info in documentation that I can find. Or is this customary?
Comment #2
hgmichna commentedMy take is that these are caused by defects in Drupal. I think they should be fixed, but only the Drupal developers can fix them.
In my version of MySQL these defects don't seem to cause any functional errors. They probably lower the performance though.
Comment #3
Sunshiney commentedI was able to fix my warnings. I used "repair" in phpmyadmin
Comment #4
hgmichna commentedAre you really sure? The repair command does nothing of the sort for me.
Comment #5
gbaudoin commentedPlease retry with the latest 6.x version, re-open this report if necessary.
Comment #6
hgmichna commentedYes, seems to be allright now. Thanks!
I did find only this warning, which seems to be harmless, in the table 'users':
"Found row where the auto_increment column has the value 0"
So no serious problem any more. I guess this issue can be closed.
Comment #7
mdupontEverything's right then, D6 has indeed a user #0 (anonymous user). This has been changed in D7.