column last_click - difference on: type
declared: array('description' => 'TODO: please describe this field!', 'type' => 'DATETIME')
actual: array('description' => 'Date/time of the last click', 'type' => 'datetime', 'not null' => FALSE)
column last_checked - difference on: type
declared: array('description' => 'TODO: please describe this field!', 'type' => 'DATETIME')
actual: array('description' => 'Date/time of the last validity check', 'type' => 'datetime', 'not null' => FALSE)

Comments

GStegemann’s picture

GStegemann CreditAttribution: GStegemann commented
Status: Active » Postponed (maintainer needs more info)

I think this is more or less a spelling issue. The schema is defined correctly. 

'last_click' => array(
   'description' => 'Date/time of the last click',
   'type' => 'datetime',
   'mysql_type' => 'DATETIME',
   ),
'last_checked' => array(
    'description' => 'Date/time of the last validity check',
    'type' => 'datetime',
    'mysql_type' => 'DATETIME',
    ),

When starting the migration of Web Links from D6 to D7 a patch was proposed to specify the column type DATETIME in upper case. However, MySQL stores it in lower case. Most probably specifying DATETIME in lower case will also work.

Gerhard

Starminder’s picture

Starminder CreditAttribution: Starminder commented

I agree it is very minor and inconsequential, however, it gets reported by the schema module as a mismatch.

GStegemann’s picture

GStegemann CreditAttribution: GStegemann commented

Yes.

But the schema module reports similar 'mismatches' for other modules as well. But you can disable this in the configuration settings of the schema module.