By Chronistin on

I finally dared to upgrade my 4.5.0 to 4.6.0 . running the Update script, I get the following error:

user error: Duplicate entry '56-239' for key 1
query: ALTER TABLE term_node ADD PRIMARY KEY (tid,nid) in /home/httpd/vhosts/skydance.at/httpdocs/includes/database.mysql.inc on line 66.

ALTER TABLE {term_node} ADD PRIMARY KEY (tid,nid)
FAILED

Looked into the database, and just about all of the "tid" values are there multiple times.

The site seems to work fine, though.

What can I do? Is this critical?

thanks,
Chronistin

Comments

Chronistin’s picture

Chronistin commented

Through google site search I found a hint to be sure to only upgrade the necessary mysql-updates. I reinstalled the database and did just that, but got the same error.

Then I searched some more and found this, but I'm not sure how to do it (i.e. which of the duplicates to remove)?

Could someone tell me what happens if the duplicates are removed? Is it now impossible to have more than one term for a node? Or is term_node for something completely different? What happens if the table is just emptied?

thanks,
Chronistin

laura s’s picture

laura s commented

There are quite a few threads on the update of the database. Basically use the oldest script that might apply to your database. You should be able to run the script without any errors. If you get errors, just run the next script, then the next, until it finally runs without errors.

There's much more detailed info in these other threads. Search for "update 4.6.0." Once you find the right script, everything should be fine.
===
Laura
pingV

_____ ____ ___ __ _ _
Laura Scott :: design » blog » tweet

Chronistin’s picture

Chronistin commented

Thanks for your input, but I did all that (trying different upgrade dates & searching for every phrase that seemed related) without success.

After half a day of database-restoring, upgrading & reading I switched to the trial & error-method. Any sql-professional would probably have seen that, but it took me some time to figure out that neither tid nor nid need to be unique in term_node - just had to make sure that there are no identical rows.

So, everything is working good now.