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

yched’s picture

Status: Active » Fixed

Right, fixed.
Not really serious, I guess. Next release will fix this next time you run update.php

polarbear128’s picture

Status: Fixed » Active

Sorry, 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?

yched’s picture

Status: Active » Fixed

Never mind about disp-width, it's not significant and Schema won't notify about it.
Issue is fixed

polarbear128’s picture

ah, 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.

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.