Version 3.8 Install Issue

Hi darshi,

I tried running drush updb, I got the following result: No database updates required
So I looked at flag.install, and function flag_update_7301() is in the file.
I tried to run that update using:
drush php-eval 'module_load_install('flag');flag_update_7301();'
It errors out, the stack trace gave me this information:
exception 'DatabaseSchemaObjectExistsException' with message 'Cannot rename flag_content to flagging: table flagging already exists.'
Next I remarked out //db_rename_table('flag_content', 'flagging'); function flag_update_7301() and ran the update, it renamed flags to flag.

I guess I will need to run the remaining updates the same way. I am doing this work in my local environment, I do not want to change my production environment in this way.

Any ideas?

Thank you,

Brian.

Hi joachim and darshi,

Thank you for helping with this issue. I looked at the site on my dev/test server and my production server (which I have not updated yet). I can confirm we are using flag version 7.x-2.2. Looking at the database tables (on dev and prod) I see the tables flags, flag_content, and flagging - which surprised me, as the update attempts to rename flag_content to flagging, right?

Also, I just remembered this is a Drupal Commons install, so perhaps the Commons distribution did some custom work with Flag or created a flagging table?

As an update, I was able to get my local up and running without error after manually running the database updates as described above. Since this is just my local I'll delete the site and re-clone the repo. I'll let you know how it works out. And thank you both very much again for helping with this issue.

Brian.

Hi joachim and darshi,

I deleted my local site, cloned the repo and copied down the database. After updating the module from 2.2 to 3.9 I ran into the same issues as above. I was puzzled by the table flagging existing in the database with version 2.2 so I examined our git log to look for changes to the module. Sure enough, the module was updated over a year ago to the 7.x-3.x branch, then a month later the 3.x version of the module was deleted from the code (not uninstalled) and the 2.2 version added back. Since not uninstalled, the database schema was not changed from the 3.x update(s).

So, the problem I have reported is a problem we caused ourselves, not an issue with your update. I apologize for wasting your time, and I thank you again for your help.

Brian.