Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#6937 closed task (blessed) (invalid)

problem with tables in phpmyadmin 2.9.2

Reported by: wep Owned by: ryan
Priority: high Milestone:
Component: General Version: 2.5.1
Severity: major Keywords:
Cc:

Description

Hi, this problem in wpmu 1.5RC1 and wp 2.5.1 because is exactly the schema...

when install, in phpmyadmin 2.9.2 in tables: wp_1_comments :

Indexes: Documentation Keyname Type Cardinality Action Field

PRIMARY PRIMARY 0 Edit Drop comment_ID comment_approved INDEX None Edit Drop comment_approved comment_post_ID INDEX None Edit Drop comment_post_ID comment_approved_date_gmt INDEX None Edit Drop comment_approved comment_date_gmt comment_date_gmt INDEX None Edit Drop comment_date_gmt ! More than one INDEX key was created for column comment_approved <------ Warning

click in edit comment_aproved and: ("PRIMARY" must be the name of and only of a primary key!) <----- Warning

Change History (2)

  • Resolution set to invalid
  • Status changed from new to closed

PHPMyAdmin complains about the column being used in two or more indexes. It doesn't mean that it is a bug, just that the owner of the table might had made a mistake. However, I think the usage of the indexes is for performance, so this is intentional.

  • Milestone 2.7 deleted
Note: See TracTickets for help on using tickets.