Here:

watcher_nodes

column mail:
declared: array('type' => 'varchar', 'length' => 128, 'default' => )
actual: array('type' => 'varchar', 'length' => '128', 'not null' => TRUE, 'default' => '')

column watch_for:
declared: array('type' => 'int', 'size' => 'tiny', 'default' => )
actual: array('type' => 'int', 'size' => 'tiny', 'not null' => FALSE, 'disp-width' => '4')

column watch_for: key 'not null' not set, ignoring inspected default value

Comments

solipsist’s picture

solipsist commented
Version: 6.x-1.3 » 6.x-1.x-dev
Status: Active » Fixed

Thanks for reporting. Will be fixed in the next release.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Paul Simard’s picture

Paul Simard commented
Title: schema module reports mismatching tables (no big deal but - necessary to fix ) » (2nd time around) schema module reports mismatching tables (no big deal but - necessary to fix )
Version: 6.x-1.x-dev » 7.x-1.x-dev
Assigned: Unassigned » Paul Simard
Issue summary: View changes
Status: Closed (fixed) » Active

Using schema.

Installed watcher normally. OK. Schema then reported mismatches (5) in the status report.

Errors reported were:

  • watcher_nodes.uid is part of the primary key but is not specified to be 'not null'.
  • watcher_nodes.nid is part of the primary key but is not specified to be 'not null'.
  • watcher_nodes.mail is part of the primary key but is not specified to be 'not null'.
  • watcher_notify_queue.qid is part of the primary key but is not specified to be 'not null'.
  • watcher_user_settings.uid is part of the primary key but is not specified to be 'not null'.

This error was originally reported on V6.x-1.3-dev and closed (fixed) automatically 2 weeks later due to inactivity.

I will endeavor to repair and post a patch.

Paul Simard’s picture

Paul Simard commented
Issue tags: +Novice
Paul Simard’s picture

Paul Simard commented
Assigned: Paul Simard » Unassigned

Sorry, have to bail on this, due to time constraints and a commercial project.