xmlsitemap_node.nid is part of the primary key but is not specified to be 'not null'.
Tables for which the schema and database are different.
- column nid:
declared: array('type' => 'int', 'unsigned' => TRUE)
actual: array('type' => 'int', 'unsigned' => TRUE, 'not null' => TRUE, 'default' => 0, 'disp-width' => '10') - column nid:
declared: array('type' => 'int', 'unsigned' => TRUE)
actual: array('type' => 'int', 'unsigned' => TRUE, 'not null' => TRUE, 'default' => 0, 'disp-width' => '10') - column pid: key 'not null' not set, ignoring inspected default value
- column last_changed: key 'not null' not set, ignoring inspected default value
- column previously_changed: key 'not null' not set, ignoring inspected default value
- column last_comment: key 'not null' not set, ignoring inspected default value
- column previous_comment: key 'not null' not set, ignoring inspected default value
- column priority_override: key 'not null' not set, ignoring inspected default value
thanks for nice module.
Comments
Comment #1
avpadernoI agree on the fact that primary keys, unique keys, and indexes must be not null, but I don't understand what means declared, and actual.
I am sure that Drupal schema uses some default values for the fields definition, and declaring a module database table not explicating a value to use the default one is not a bug.
I changed the referring version to 6.x-1.x-dev because it's there where new code, and fixes go.
Comment #2
avpadernoThe primary key is now declared NOT NULL.
It has been fixed in CVS. Thanks for your report.