First, the specifics:
This is occurring with a core install, both 4.7 and last night's CVS.
Apache/2.2.0 (Win32), PHP/5.1.2, MySQL 5.0.18, phpMyAdmin - 2.8.0.4

Drupal 4.7 errors:

Problems with indexes of table `node`
PRIMARY and INDEX keys should not both be set for column `nid`
More than one INDEX key was created for column `status`
Problems with indexes of table `term_hierarchy`
PRIMARY and INDEX keys should not both be set for column `tid`
Problems with indexes of table `term_node`
PRIMARY and INDEX keys should not both be set for column `tid`

Drupal CVS errors:

Problems with indexes of table `node`
More than one INDEX key was created for column `status`
Problems with indexes of table `term_hierarchy`
PRIMARY and INDEX keys should not both be set for column `tid`
Problems with indexes of table `term_node`
PRIMARY and INDEX keys should not both be set for column `tid`

Why I am taking this seriously:

Besides that this seemingly compounds similar issues with contributed modules, it later becomes impossible to update database records at all. While I was able to locate this posting: http://drupal.org/node/21876 -- I figured this was worth bringing up, since this is happening with an out-of-the-box core mysql install (both 4.0/4.1, for the sake of being thorough).

As an example:

Problems with indexes of table `category_cont_distant`
PRIMARY and INDEX keys should not both be set for column `cid`
Problems with indexes of table `category_hierarchy`
PRIMARY and INDEX keys should not both be set for column `cid`
Problems with indexes of table `category_node`
PRIMARY and INDEX keys should not both be set for column `cid`
Problems with indexes of table `node`
PRIMARY and INDEX keys should not both be set for column `nid`
More than one INDEX key was created for column `status`
Problems with indexes of table `nodevote`
PRIMARY and INDEX keys should not both be set for column `uid`
Problems with indexes of table `shoutbox_moderation`
PRIMARY and INDEX keys should not both be set for column `moderation_id`
Problems with indexes of table `station_playlist_track`
More than one INDEX key was created for column `title`
Problems with indexes of table `term_hierarchy`
PRIMARY and INDEX keys should not both be set for column `tid`
Problems with indexes of table `term_node`
PRIMARY and INDEX keys should not both be set for column `tid`
Problems with indexes of table `view_view`
UNIQUE and INDEX keys should not both be set for column `name`

At the point where these database errors turn up, I have been attempting to create tinymce profiles for various roles I have created; once the profile is saved, I can no longer edit nor delete them (the tables in the database either become duplicated or simply won't budge).

Since this isn't dinging a lot of people, I wouldn't quite write home about this one, but I figured it was worth pointing out since it seems reasonable that these types of problems could result in folks who discover that their databases have begun to go south...

(Looking forward to seeing if there is a response to this)

Comments

Max Bell’s picture

Assigned: Unassigned » Max Bell
Status: Active » Closed (fixed)

I have since learned that the errors in question are not always necessarily errors, per the designers of phpMyAdmin, and have since managed to produce a working installation (reproducible!) that does not have this same problem.

(Dangit! I thought I'd found something! Oh, well. At least I can close my own issue.)

bryansd’s picture

Version: 4.7.0 » 4.7.2

I'm leaving this ticket closed, but just wanted to report that I found this same error for some of my tables, notably the node table. Sometimes it helps identify problems others have seen in case the problem is not found to be benign down the road.

I do seem to have some problems when it comes to updating contributed modules...but the site in question also has some history of testing cvs modules before they're ready. My database is MySQL 4.1.19-standard.

-Bryan