Changes between Version 7 and Version 8 of DbChanges


Ignore:
Timestamp:
2010-07-15T05:06:22Z (14 years ago)
Author:
Pan Luo
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DbChanges

    v7 v8  
    88 * The *exact and complete* SQL statement that will perform the change.
    99
     10==== July 15, 2010 ====
     11Adding database version control for upgrading.
     12{{{
     13#!sql
     14INSERT INTO `sys_parameters` ( `parameter_code` , `parameter_value` , `parameter_type` , `description` , `record_status` , `creator_id` , `created` , `updater_id` , `modified` )
     15VALUES ('database.version', '1', 'I', 'database version', 'A', '0', '0000-00-00 00:00:00', NULL , NULL);
     16}}}
     17
    1018==== June 16, 2010 ====
    1119This change was made for student's survey evaluation submissions. Since students submitting surveys are not tied to groups, their group values will be should NULL. Before, the default value for grp_event_id was zero, and, because of the relationship grp_event_id and submitter_id (onl one pair is allowed), the effect was that a single student could only submit one Survey, ever. This change remedies the situation, and no code needs to be changed to accommodate it. - Serge & Pan
    1220{{{
     21#!sql
    1322ALTER TABLE `ipeer`.`evaluation_submissions` MODIFY COLUMN `grp_event_id` INTEGER  DEFAULT NULL;
    1423}}}
     
    1726This change is made for student's rubrics evaluation submissions. Since students submitted rubric evaluations are not tied to the rubric, deleting a rubric does not fully remove students' evaluation data of that rubric. With the added 'rubric_id' field, the linkage is now complete and references would not be lost in the relationship specified between evaluation_rubrics and rubric tables.  - Henry
    1827{{{
     28#!sql
    1929ALTER TABLE evaluation_rubrics ADD COLUMN rubric_id INTEGER DEFAULT 0 NOT NULL;
    2030}}}