After recent Mollom update, the Schema module started reporting this mismatch:

column captcha_id - differences on: not null, default
declared: array('description' => 'TODO: please describe this field!', 'type' => 'varchar', 'length' => 128, 'not null' => TRUE, 'default' => '')
actual: array('description' => 'CAPTCHA ID returned by Mollom.', 'type' => 'varchar', 'length' => '128', 'not null' => FALSE)

CommentFileSizeAuthor
#1 mollom.schema.1.patch1.32 KBeshta

Comments

eshta’s picture

eshta commented
Status: Active » Needs review
StatusFileSize
new mollom.schema.1.patch1.32 KB

Adding a patch to address this with an additional update. Also fixing the index definition of the main schema change update.

jaydee1818’s picture

jaydee1818 commented

Thanks it worked, but I had to uninstall and then reinstall the module (which was a pain). Should running updatedb have prevented the need for that? Because it didn't for me. Cheers.

eshta’s picture

eshta commented

Hmmm... the update hook should have handled updating the schema of the database table to match the defined schema. Certainly an uninstall/reinstall is not an acceptable upgrade path ;-)

@jaydee1818 It's going to take a bit of extra time to set up an environment to test this out but I'll see if I can find out what happened with the upgrade script. Did you get any errors or have any additional information in your logs after you ran the update.php and before the uninstall that may help in troubleshooting?

jaydee1818’s picture

jaydee1818 commented

No errors in my log. When I ran updatedb, I definitely got a message telling me that something to do with the captcha schema was going to be altered. I guess it perhaps didn't alter as the Schema module continued to report mollom tables as a mismatch until I uninstalled/reinstalled. Cheers.