I have updated from beta2 to beta3. Run update.php, and:
- user warning: Can't DROP 'name_2'. Check that column/key exists query: ALTER TABLE oblivionpower_panels_page DROP INDEX name_2 in /htdocs/drupal/includes/database.mysql.inc on line 172.
- user warning: Can't DROP 'oblivionpower_panels_object_cache_idx'. Check that column/key exists query: ALTER TABLE oblivionpower_panels_object_cache DROP INDEX oblivionpower_panels_object_cache_idx in /htdocs/drupal/includes/database.mysql.inc on line 172.
and:
The following queries were executed
panels module
Update #5215
- ALTER TABLE {panels_object_cache} CHANGE COLUMN data data longtext
- ALTER TABLE {panels_mini} DROP INDEX name_2
- Failed: ALTER TABLE {panels_page} DROP INDEX name_2
- Failed: ALTER TABLE {panels_object_cache} DROP INDEX {panels_object_cache}_idx
- ALTER TABLE {panels_pane} ADD PRIMARY KEY (pid)
Can you help me?
Thanks.
Frank
Comments
Comment #1
nath commentedSimilar here:
and:
Comment #2
nath commentedIt seems, in my DB, the superfluous index that should be dropped isn't called name_2 but panels_mini_name_idx / panels_page_name_idx and in panels_object_cache, there was no duplicated index.
Also, there are multiple lines with pid 0 and the rest more or less empty in panels_pane, which is why the change failed as well.
I guess, removing the two indexes and the lines with pid 0 (and adding the primary key afterwards) should be enough to fix this?
Comment #3
buzzdecafe commentedSimilar here, too:
and
Comment #4
sdboyer commentedI really should have included an informative message to assuage peoples' concerns over this in the update, or figured out a way to determine if there were any duplicate indexes before attempting to drop them. Sorry.
In a previous version of Panels2, duplicate indexes were accidentally created - but, evidently, only for some people, and some other people had different duplicate indexes created (as in nath's case in #2). However, here's the bottom line:
If one of the 'DROP INDEX' queries fails while you're running update.php, NOTHING is wrong. Panels should NOT be broken.
However, if the ADD PRIMARY KEY query fails, you do have a problem, but nath, the steps you outline in #2 should fix your problem, at least.
Unfortunately, Panels2 is complex enough that odd cases like this do seem to arise periodically, so there's only so much I can do in the update scripts.
Comment #5
matshuk commentedComment #6
tyler-durden commentedThat was the problem. Doh!