I think I found the problem .. but I need you to verify.
This messed me around for a full day today!
----
In the 1.5.2--> 1.5.3 update sql file, the following occurs:
# assignments table
CREATE TABLE `assignments` (
`assignment_id` MEDIUMINT(6) UNSIGNED NOT NULL AUTO_INCREMENT,
`course_id` MEDIUMINT UNSIGNED NOT NULL default '',
`title` VARCHAR(60) NOT NULL default '',
`assign_to` MEDIUMINT UNSIGNED DEFAULT 0,
`date_due` DATETIME NOT NULL DEFAULT '0000-00-00 00:00:00',
`date_cutoff` DATETIME NOT NULL DEFAULT '0000-00-00 00:00:00',
`multi_submit` TINYINT DEFAULT '0',
PRIMARY KEY (`assignment_id`),
INDEX (`course_id`)
) TYPE = MYISAM;
# --------------------------------------------------------
## assignment manager
CREATE TABLE `assignments` (
`assignment_id` MEDIUMINT(6) UNSIGNED NOT NULL AUTO_INCREMENT,
`course_id` MEDIUMINT UNSIGNED NOT NULL default '',
`title` VARCHAR(60) NOT NULL default '',
`assign_to` MEDIUMINT UNSIGNED DEFAULT 0,
`date_due` DATETIME NOT NULL DEFAULT '0000-00-00 00:00:00',
`date_cutoff` DATETIME NOT NULL DEFAULT '0000-00-00 00:00:00',
`multi_submit` TINYINT DEFAULT '0',
PRIMARY KEY (`assignment_id`),
INDEX (`course_id`)
) TYPE = MYISAM;
=====
In the schema.sql file:
# --------------------------------------------------------
# Table structure for table `assignments`
# since 1.5.3
CREATE TABLE `assignments` (
`assignment_id` MEDIUMINT UNSIGNED NOT NULL AUTO_INCREMENT,
`course_id` MEDIUMINT UNSIGNED NOT NULL default 0,
`title` VARCHAR(60) NOT NULL default '',
`assign_to` MEDIUMINT UNSIGNED default 0,
`date_due` DATETIME NOT NULL DEFAULT '0000-00-00 00:00:00',
`date_cutoff` DATETIME NOT NULL DEFAULT '0000-00-00 00:00:00',
`multi_submit` TINYINT DEFAULT '0',
PRIMARY KEY (`assignment_id`),
INDEX (`course_id`)
) TYPE = MYISAM;
======
Should not the schema code not be in the update one (including the default value of 0 for the course_id in:
`course_id` MEDIUMINT UNSIGNED NOT NULL default 0,
Also, is not the second occurance in the update sql not an incorrect redundancy?
thanks
larry