UNIQUE and INDEX keys should not both be set for column `ID_TOPIC`

Started by Niteblade, July 03, 2006, 07:42:13 PM

Previous topic - Next topic

Niteblade

SMF Version: SMF 1.1 RC2
(Shared hosting.)

Through phpmyadmin, I goto my database.

I tick off All Tables, then run a "Check Table" on them.

Here is the result ... everything gives a msg_type of "OK" except for "smf_log_floodcontrol" which gives a msg_type of "The storage engine for the table doesn't support check"

There is only one message at the bottom ...

Quote
Problems with indexes of table `smf_messages`
UNIQUE and INDEX keys should not both be set for column `ID_TOPIC`

Does this represent a problem or a conflict with one of my mods ? I know that one badly structured mysql query can slow the entire database down.

What should I do ? Leave it alone ? Change it ? Modify it ? (Modify it to what ?)

Keyname      Type    Cardinality    Action       Field
------------------------------------------------
PRIMARY       PRIMARY    75       Edit/Drop     ID_MSG 
topic            UNIQUE      75       Edit/Drop     ID_TOPIC 
ID_MSG                                  Edit/Drop     
ID_BOARD      UNIQUE     75       Edit/Drop      ID_BOARD 
ID_MSG                                  Edit/Drop     
ipIndex          INDEX       75       Edit/Drop      posterIP 15 
ID_TOPIC                                Edit/Drop
participation   INDEX       75       Edit/Drop      ID_MEMBER 
ID_TOPIC                                Edit/Drop     
ID_TOPIC       INDEX       37       Edit/Drop      ID_TOPIC 
UNIQUE and INDEX keys should not both be set for column `ID_TOPIC'


affiliate blog

Ben_S

This is not a problem and is intended, phpMyAdmin doesn't seem to understand that there are times when people might want more than one index on a column.
Liverpool FC Forum with 14 million+ posts.

Advertisement: