Closed (works as designed)
Project:
Related links
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
28 Feb 2011 at 07:34 UTC
Updated:
15 May 2012 at 19:32 UTC
relatedlinks
column nid - difference on: not null
declared: array('description' => t('TODO: please describe this field!'), 'type' => 'int', 'unsigned' => TRUE, 'default' => 0)
actual: array('description' => t('TODO: please describe this field!'), 'type' => 'int', 'unsigned' => TRUE, 'not null' => TRUE, 'default' => 0)
Comments
Comment #1
Zen commentedIt really shouldn't matter. Having a not null is best and if you don't have it, you can add it. The module's schema already has a not null set.
I'm not sure how it got in. But if it did, it's probably a vestige from D5? I'm going to mark this as a 'works as designed' for the moment.
-K