I did the update per the update page on two versions and I keep getting SQL table dup errors. Thanks for your help.

* user warning: Duplicate column name 'shown' query: ALTER TABLE panels_pane ADD COLUMN shown int(1) DEFAULT 1 AFTER subtype in /home/w/html/includes/database.mysqli.inc on line 151.
* user warning: Duplicate column name 'title' query: ALTER TABLE panels_display ADD COLUMN title varchar(128) AFTER cache in /home/w/html/includes/database.mysqli.inc on line 151.
* user warning: Duplicate column name 'hide_title' query: ALTER TABLE panels_display ADD COLUMN hide_title int(1) AFTER title in /home/w/html/includes/database.mysqli.inc on line 151.
* user warning: Duplicate column name 'visibility' query: ALTER TABLE panels_pane ADD COLUMN visibility text AFTER access in /home/w/html/includes/database.mysqli.inc on line 151.
* user warning: Duplicate column name 'switcher_type' query: ALTER TABLE panels_page ADD COLUMN switcher_type varchar(128) AFTER no_blocks in /home/w/html/includes/database.mysqli.inc on line 151.
* user warning: Duplicate column name 'switcher_name' query: ALTER TABLE panels_page ADD COLUMN switcher_name varchar(128) AFTER no_blocks in /home/w/html/includes/database.mysqli.inc on line 151.
* user warning: Duplicate column name 'switcher_options' query: ALTER TABLE panels_page ADD COLUMN switcher_options longtext AFTER switcher_type in /home/w/html/includes/database.mysqli.inc on line 151.

panels module
Update #5216

* Failed: ALTER TABLE {panels_pane} ADD COLUMN shown int(1) DEFAULT 1 AFTER subtype
* Failed: ALTER TABLE {panels_display} ADD COLUMN title varchar(128) AFTER cache
* Failed: ALTER TABLE {panels_display} ADD COLUMN hide_title int(1) AFTER title
* ALTER TABLE {panels_display} DROP COLUMN name
* Failed: ALTER TABLE {panels_pane} ADD COLUMN visibility text AFTER access

Update #5217

* Failed: ALTER TABLE {panels_page} ADD COLUMN switcher_type varchar(128) AFTER no_blocks
* Failed: ALTER TABLE {panels_page} ADD COLUMN switcher_name varchar(128) AFTER no_blocks
* Failed: ALTER TABLE {panels_page} ADD COLUMN switcher_options longtext AFTER switcher_type

Update #5218

* No queries

Comments

dubbelD-1’s picture

dubbelD-1 commented

Any updates on the source of this?

I'm seeing the same problem

sdboyer’s picture

sdboyer commented
Status: Active » Closed (works as designed)

Hmmm...this may well be evidence that what we really need to do is start being more scrupulous about putting the updates to client modules into the .install files for those client modules, where they really belong...

Anyway. I don't know how you got your version of Panels to this weird, in-between state with the database tables, but the bottom line is that none of the errors you listed above are actually indicative of any problems. Failing to add/drop a column because that operation was already done may spit out an ugly-looking error, but it doesn't do any actual harm.

So, the update on this is that I'm marking this by design, because the error messages you're reporting are indicative that a) your panels installation should be running without any problems, and b) that you did something nonstandard in the way you handled your updates, or maybe you ran a -dev version of Panels and ran update.php. Whatever the case, it's an irregularity on your end that simply has too many possible causes for it to be feasible for me to help you debug simply from those messages.

dubbelD-1’s picture

dubbelD-1 commented
Status: Closed (works as designed) » Active

I'm wondering if this is related to this issue - http://drupal.org/node/262525?

Anyone know?

sdboyer’s picture

sdboyer commented
Status: Active » Closed (works as designed)

Re-opening the issue in order to simply ask whether or not the issue is a duplicate is rude. Don't do it please, especially if you want my help.

Also, you might consider addressing some of the issues I raised in my post, rather than just ignoring them and asking another question.

Again, the bottom line: sure, it _could_ be related to #262525: Updating from 5.x-2.x-beta3-dev to beta4, just like it _could_ be related to a lot of things. But again - the error messages provided are not indicative of there being any actual problem, and until someone offers evidence that their Panels install actually isn't working, then I'm not sure what the point of the issue is.

yuetsu’s picture

yuetsu commented

i ran into a similar problem when i re-ran the db update after installing the latest "mollom" module for it, even tho' it showed no update necessary. i didn't have all the lines the original person (venusrising) had in the error, just one. but basically it was a db error saying it couldn't add the db column because it was a duplicate of one already in there. this makes perfect sense if the db update is being re-run when it doesn't need to be — he script is trying to ad a column with the same name that it doesn't need to, because it has already been created. i'd check if you'd already run the db update for whatever module you've updated before, and if it has already been run, don't bother. all tables & columns you need are already in there.

but this raises a question — should a bug or feature request be filed? the error would be better if it said something along the lines of "you've already run this db update, the column/table you're trying to add is already there..." then continued on with the duplicate error message, or something like that. or just halts the script if it knows you're trying to add something to the db that's already in there and doesn't need updating. what say you folks? file it as a bug? feature request? don't bother?