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.
A couple of these need work -- patch is at http://drupal.org/node/968404#comment-3851236
Comment | File | Size | Author |
---|---|---|---|
#2 | image.update-6104.2.patch | 2.18 KB | sun |
#1 | 1004608.image_.clean-up-hook_update_N.patch | 1.86 KB | joachim |
Comments
Comment #1
joachim CreditAttribution: joachim commentedThis is the patch from over there.
However, API says:
> IMPORTANT NOTE: To maintain database portability, you have to explicitly recreate all indices and primary keys that are using the changed field.
and we have this:
> 'primary key' => array('nid', 'image_size'),
Hence needs work.
Comment #2
sunThanks for reviewing, good spot! Committed to D6.
A new development snapshot will be available within the next 12 hours. This improvement will be available in the next official release.
Comment #3
heyyo CreditAttribution: heyyo commentedwith the last dev I still have this schema errors :
Comment #4
joachim CreditAttribution: joachim commentedWhere do you get that message?
Also, I don't see the text ''TODO: please describe this field!'' in either Image module or core.
Comment #5
sunSchema module produces such messages, when checking the actual database table schema against the module-defined schema.
@heyyo: Do you know which version of Image module you initially installed?
Comment #6
heyyo CreditAttribution: heyyo commentedI really don't know which version I started to use, but it was a long time ago...maybe in january 2009 with acquia distribution of drupal 6. Never mind I created an index on fid with phpmyadmin.
Comment #7
sunAfter closely inspecting the update functions once again, update 6100 should have set the correct schema info already. I can only guess that this update already ran on your site.