Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hi, just upgraded from 6.x-2.0-rc5 to 6.x-2.0-rc6, and the Schema module is reporting a mismatch:
In the content table
* content_node_field
o column locked:
declared: array('type' => 'int', 'size' => 'tiny', 'not null' => TRUE, 'default' => 0)
actual: array('type' => 'int', 'size' => 'tiny', 'not null' => FALSE, 'default' => 0, 'disp-width' => '4')
does the schema for content need to be changed?
Cheers
Comments
Comment #1
yched CreditAttribution: yched commentedRight, fixed.
Not really serious, I guess. Next release will fix this next time you run update.php
Comment #2
polarbear128 CreditAttribution: polarbear128 commentedSorry, I should say its the content_node_field table.
The weird thing is that looking at the table in mysql, I can see that the "locked" field is declared as tinyint(4), same as the "active" field above it, with no mention of disp-width....not sure how that translates to db.
Also if I change the content.install file to include the disp-width attribute, it makes no difference to the Schema module.
Ah, but if I modify the whole of $schema['content_node_field'] in content.install to what is given on the Schema module Inspect tab, the issue goes away.
Is it just a badly written schema spec?
Comment #3
yched CreditAttribution: yched commentedNever mind about disp-width, it's not significant and Schema won't notify about it.
Issue is fixed
Comment #4
polarbear128 CreditAttribution: polarbear128 commentedah, sorry, i must have been adding info to my issue when you altered the status to fixed...and it auto-changed to active
Thanks for the quick response.
Comment #5
Anonymous (not verified) CreditAttribution: Anonymous commentedAutomatically closed -- issue fixed for two weeks with no activity.