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.
I installed the schema module and it reports some length mismatches in the db tables regarding feeds_imagegrabber. Here they are:
* column enabled - difference on: length
declared: array('description' => t('TODO: please describe this field!'), 'type' => 'int', 'unsigned' => TRUE, 'length' => '1', 'not null' => TRUE, 'default' => 0)
actual: array('description' => t('TODO: please describe this field!'), 'type' => 'int', 'unsigned' => TRUE, 'not null' => TRUE, 'default' => 0)
* column id_class - difference on: length
declared: array('description' => t('TODO: please describe this field!'), 'type' => 'int', 'unsigned' => TRUE, 'length' => '2', 'not null' => TRUE, 'default' => 0)
actual: array('description' => t('TODO: please describe this field!'), 'type' => 'int', 'unsigned' => TRUE, 'not null' => TRUE, 'default' => 0)
* column feeling_lucky - difference on: length
declared: array('description' => t('TODO: please describe this field!'), 'type' => 'int', 'unsigned' => TRUE, 'length' => '1', 'not null' => TRUE, 'default' => 0)
actual: array('description' => t('TODO: please describe this field!'), 'type' => 'int', 'unsigned' => TRUE, 'not null' => TRUE, 'default' => 0)
* column exec_time - difference on: length
declared: array('description' => t('TODO: please describe this field!'), 'type' => 'int', 'unsigned' => TRUE, 'length' => '3', 'not null' => TRUE, 'default' => 10)
actual: array('description' => t('TODO: please describe this field!'), 'type' => 'int', 'unsigned' => TRUE, 'not null' => TRUE, 'default' => 10)
They all seem to be about the length values of the fields.
Comments
Comment #1
publicmind CreditAttribution: publicmind commentedAccording to http://drupal.org/node/146939, 'length' is valid parameter for type 'int'. I am not sure for the source of error, may be mysql doesn't pay regard to the 'length' parameter for type 'int'.
Comment #2
klonosI honestly couldn't know. I am simply reporting it.
I know that I can go and manually change the lengths in the db myself and the warning will go away. I don't know if I should do so though and what that would do to the module. Anyways, since this is an actively maintained module, I think its best to correct the issue at its root rather than working around it. History has taught me that leaving things the way they are might come back and bite you at a later point (when you least expect it).
Thank you for taking the time to look into this one.
Comment #3
publicmind CreditAttribution: publicmind commentedI agree, thanks for reporting.
But did you try to change the length of the field in the database table. I tried, but the warning isn't going away. Also on installing a new schema, it doesn't seem like 'length' parameter is respected for type 'int'. I will debug a little more and will appropriately in the Schema issue queue as well the Drupal queue, as now I am pretty sure that FIG is doing nothing wrong.
Regards,
Comment #4
klonosThank you for taking the time. Please post here links to any related issues you might open in other queues.
Comment #5
publicmind CreditAttribution: publicmind commentedHi,
I have reported the issues in both Drupal as well as Schema issue queue:
http://drupal.org/node/764026
http://drupal.org/node/764064
I am interested to see the solution.
Regards,
Comment #6
klonosSince the issue is not fixed nor closed, please keep it set to 'postponed' till we have any news from any of these issues. Thank you.
Comment #7
publicmind CreditAttribution: publicmind commentedIt looks like there was a documentation error. fixed in dev.
Comment #8
publicmind CreditAttribution: publicmind commentedIt looks like there was a documentation error. fixed in dev.
Comment #9
klonosconfirming fixed in dev. thanx