Closed (fixed)
Project:
Privatemsg
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
11 Nov 2010 at 00:29 UTC
Updated:
7 Mar 2011 at 01:51 UTC
Jump to comment: Most recent file
Hello,
I'm curious if this is an error that I can ignore. I upgraded from 6.x-1.3 to 6.x-2.x-dev and got this error (all other messages were fine)
"Can't DROP 'uid'; check that column/key exists query: ALTER TABLE pm_index DROP INDEX uid in /home/****/public_html/includes/database.mysql-common.inc on line 448"
Thank you for your help
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | fix_upgrade_path_and_add_better_indexes_for_2x_too.patch | 6.89 KB | berdir |
| #3 | fix_upgrade_path_and_add_better_indexes.patch | 4.56 KB | berdir |
Comments
Comment #1
berdirYes, you can ignore this.
We renamed that in 6.x-1.3, that's why it doesn't work anymore.
It will produce a problem for PostgreSQL users, however, I'll look into it.
Comment #2
Ela commentedThank you :)
Comment #3
berdirThe following patch should fix all reported errors in the 6.x-1.x to 6.x-2.x upgrade path.
Note that only this means that only upgrading from 6.x-1.3 or later is supported now.
Comment #4
berdirComment #5
Ela commentedShould I still apply this patch even though I have 2.x running already?
Comment #6
berdirNo, this won't help you, at least not the current patch.
The only thing you could do is try to repeat your upgrade with an old backup for testing purposes only, to verify that the errors are really gone now.
I will try to add a update function to improve the current 6.x-2.x installations too but this is unfortunatly not trivial because the APIs given by Drupal 6 are very limiting.
Comment #7
berdirOk, here is a new patch.
This contains a backport of the db_index_exists() function in D7 and some new update functions which will try to clean up the index mess in 6.x-2.x.
Please try the patch with whatever versions you have, this should now properly update from 6.x-1.3+ and 6.x-2.x with the same end result.
Comment #8
berdirCommited.
Comment #9
Ela commentedsorry... did not get a chance to report. As you probably know all went through without any errors :)