After installing schema module, it gave me a warning that one of the schemas were incorrect. Nothing important seems to be effected though. Here is what schema reports:

project_issue_comments
- column cid - differences on: not null, default
- declared: array('description' => t('TODO: please describe this field!'), 'type' => 'int', 'not null' => FALSE)
- actual: array('description' => t('TODO: please describe this field!'), 'type' => 'int', 'not null' => TRUE, 'default' => 0)

CommentFileSizeAuthor
#4 cid_not_null-789300-3.patch613 bytesfgm
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

waverate’s picture

waverate CreditAttribution: waverate commented

Schema module is reporting a mismatch where the schema and database are different for project_issue.

It also reports:

project_issue_comments.cid is part of the primary key but is not specified to be 'not null'.

Does this need to be cleaned up?

fgm’s picture

fgm
Primary language French
Location Paris, France
CreditAttribution: fgm commented
Version: 6.x-1.0-alpha4 » 6.x-1.0-alpha5

It should: any component of a primary key should be NOT NULL.

Issue is still there in alpha5.

dww’s picture

dww
we/he/they
CreditAttribution: dww commented

Doh, sorry. This totally fell off my radar. We'll be sure to resolve this before an official 6.x-1.0 release.

fgm’s picture

fgm
Primary language French
Location Paris, France
CreditAttribution: fgm commented
Status: Active » Needs review
FileSize
cid_not_null-789300-3.patch613 bytes

Suggested patch. It does not include a project_issue_update_6007() because the new schema is what MySQL actually implements with the current declaration.