The schema module is reporting tables for which the schema and database are different under:
simplenews_statistics
subscriber_count: not in database
send_start_timestamp: not in database
send_end_timestamp: not in database
archived: not in databasecolumn unique_opens - differences on: unsigned, default
declared: array('description' => 'TODO: please describe this field!', 'type' => 'int', 'not null' => TRUE, 'default' => -1)
actual: array('description' => 'Emailaddress-unique opens for this newsletter', 'type' => 'int', 'unsigned' => TRUE, 'not null' => TRUE, 'default' => 0)column total_opens - differences on: unsigned, default
declared: array('description' => 'TODO: please describe this field!', 'type' => 'int', 'not null' => TRUE, 'default' => -1)
actual: array('description' => 'Total opens for this newsletter', 'type' => 'int', 'unsigned' => TRUE, 'not null' => TRUE, 'default' => 0)unique_clicks: not in database
send: unexpected column in database
total_clicks: unexpected column in database
user_unique_click_through: unexpected column in database
simplenews_statistics_url
column url - difference on: not null
declared: array('description' => 'TODO: please describe this field!', 'type' => 'text', 'not null' => TRUE)
actual: array('description' => 'TODO: please describe this field!', 'type' => 'text', 'not null' => FALSE)click_count: not in database
snid: unexpected column in database
indexes nid: missing in database
simplenews_statistics_click
clid: not in database
snid: not in database
cid: unexpected column in database
primary key:
declared: array('clid')
actual: array('cid')
indexes urlid: missing in database
simplenews_statistics_open
opid: not in database
oid: unexpected column in database
primary key:
declared: array('opid')
actual: array('oid')
indexes nid: missing in database
Comments
Comment #1
dieuweHave you upgraded from an older dev version? If so, most (maybe all) of the issues with the
simplenews_statistics
table should be fixed with a database update.As for the other 3 tables, I never wrote an upgrade path because the schemas and logic were so broken no one should have been able to record any valid data in them up until they were changed.
If an upgrade path is important I can work on writing one, else I suggest you disable, uninstall, and then re-enabled the module.
Comment #2
deanflory CreditAttribution: deanflory commentedI've run update.php many times and keep most of modules up-to-date with the latest releases. It's almost certain that I've updated dev versions since most D7 modules are lingering in dev even though they're being updated. I'll just disable, uninstall and install the latest dev to see how that works.
Thanks for your time and effort!
Comment #3
deanflory CreditAttribution: deanflory commentedDisabling, uninstalling & installing the latest dev appears to have fixed this issue. I'm marking this as "Closed (won't fix)" since it's a dev issue and no upgrade path will likely be created.