Error: Database schema Inconsistent

Posted by jeff00seattle on March 11, 2009 at 5:43pm

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 value

Should I be concerned and what should I do?

Thanks

Jeff in Seattle

Comments

Getting schema mis-match issues for multiple modules

Posted by jeff00seattle on March 11, 2009 at 7:03pm

I am getting this mis-match schema issue now with multiple modules:

panels_node
panels_page
ajax_checklist

Should I file an issue with each of these modules?

Jeff in Seattle

same problem, no info...

Posted by ClearXS on May 30, 2010 at 8:59am

Very nice these general discussions, but only accidental there is response in the first minutes to hours after a new message shows up in the 'newswire' (I found this one through Google searching for database problems reported by this module and how to resolve).

But an issue? Not at the modules page that are reported inside your database, as they happen for many modules for mostly ordinary external reasons. If so; file it at the module schema that reports these errors, but doesn't say how these errors can be resolved by non-database experts.

I have similar problems and don't want to reinstall every time some of my near 250 modules or upgrades causes severe errors, while after fixing those errors and my site returns, my database is left with garbage and was repaired(ehh, 3 times higher than you report just on a one day old install that derailed ..!). But this is probably the weak point of Drupal; it serves for simple sites and with a few additional often used modules and only upgrading after other have tried that upgrade for at least a month without any error reported, but for building a complex site one needs to be an expert first.