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

publicmind’s picture

Category: bug » support

According 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'.

klonos’s picture

I 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.

publicmind’s picture

I 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,

klonos’s picture

Thank you for taking the time. Please post here links to any related issues you might open in other queues.

publicmind’s picture

Assigned: Unassigned » publicmind
Status: Active » Closed (fixed)

Hi,

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,

klonos’s picture

Status: Closed (fixed) » Postponed

Since 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.

publicmind’s picture

It looks like there was a documentation error. fixed in dev.

publicmind’s picture

Status: Postponed » Fixed

It looks like there was a documentation error. fixed in dev.

klonos’s picture

confirming fixed in dev. thanx

Status: Fixed » Closed (fixed)

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