Error: Database schema Inconsistent
jeff00seattle - March 11, 2009 - 17:43
Hi
I loaded: Schema 6.x-1.3 2008-May-07, and getting mis-matching tables errors.
I am not sure what I should do.
The follow error is present within the Modules listing:
The Schema comparison report shows:
* 27 modules with matching tables
* 5 extra tables
* 1 warnings
* 2 module with mis-matching tables
The database schema comparison report provides more details.In more detail...
Schema
panels_node.did is part of the primary key but is not specified to be 'not null'.
Mismatch (2)
Tables for which the schema and database are different.
panels_node
*
panels_node
o column did:
declared: array('type' => 'int')
actual: array('type' => 'int', 'not null' => TRUE, 'default' => 0, 'disp-width' => '11')
o column did:
declared: array('type' => 'int')
actual: array('type' => 'int', 'not null' => TRUE, 'default' => 0, 'disp-width' => '11')
o column css_id: key 'not null' not set, ignoring inspected default value
panels_page
*
panels_page
o column did:
declared: array('type' => 'int', 'default' => )
actual: array('type' => 'int', 'not null' => FALSE, 'disp-width' => '11')
o column did: key 'not null' not set, ignoring inspected default value
o column title: key 'not null' not set, ignoring inspected default value
o column access: key 'not null' not set, ignoring inspected default value
o column path: key 'not null' not set, ignoring inspected default value
o column css_id: key 'not null' not set, ignoring inspected default value
o column css: key 'not null' not set, ignoring inspected default value
o column arguments: key 'not null' not set, ignoring inspected default value
o column displays: key 'not null' not set, ignoring inspected default value
o column contexts: key 'not null' not set, ignoring inspected default value
o column relationships: key 'not null' not set, ignoring inspected default value
o column no_blocks: key 'not null' not set, ignoring inspected default value
o column menu: key 'not null' not set, ignoring inspected default value
o column menu_tab_weight: key 'not null' not set, ignoring inspected default value
o column menu_title: key 'not null' not set, ignoring inspected default value
o column menu_tab_default: key 'not null' not set, ignoring inspected default value
o column menu_tab_default_parent_type: key 'not null' not set, ignoring inspected default value
o column menu_parent_title: key 'not null' not set, ignoring inspected default value
o column menu_parent_tab_weight: key 'not null' not set, ignoring inspected default valueShould I be concerned and what should I do?
Thanks
Jeff in Seattle
Getting schema mis-match issues for multiple modules
I am getting this mis-match schema issue now with multiple modules:
Should I file an issue with each of these modules?
Jeff in Seattle
Jeff in Seattle