I've upgraded image module several times before with no problems.

However, I tried to upgrade from 5.x-1.3 to 5.x-1.4 and twice got the following error after running the database upgrade script. Any ideas what's wrong and how to solve it? 

The following queries were executed
image module
Update #4

    * Failed: DELETE FROM {file_revisions} WHERE NOT EXISTS (SELECT * FROM {files} WHERE {files}.fid = {file_revisions}.fid)

Comments

drewish’s picture

drewish commented
Status: Active » Closed (duplicate)

i'm assuming you're using a version of mysql previous to 4.1

drewish’s picture

drewish commented

sorry forgot the link: http://drupal.org/node/158264

farrell’s picture

farrell commented

Correct, 4.0.25-standard.

I reviewed the link. I use shared hosting so I can request a mysql upgrade, or are there changes coming to the module to support 4.0?

If I ask for an upgrade, what would you suggest? Mysql should be backwards compatible, correct?

drewish’s picture

drewish commented

if people want to write patches to make it backwards compatible i'll review them, but i don't have time to support mysql versions prior to 4.1. i think i'd left a comment on the other issue that the query would need to be rewritten to use an inner join rather than an exists sub query.

farrell’s picture

farrell commented

OK, thanks much. I just created a ticket to upgrade the mysql on that server to 4.1.

Should do the trick.

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented

4.1 is still unsupported. You need to request 5.x.

drewish’s picture

drewish commented

no, 4.1 should work, they added sub queries to that release... right?

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented

No, I meant it is not supported by the vendor. They have discontinued support of all realesae before 5.0.

farrell’s picture

farrell commented

Thanks for the info.

I talked to my host and they are going to upgrade to mysql 5.0.

farrell’s picture

farrell commented

Just to complete the loop, all is solved.

I upgraded to MySQL 5.0 -- as well as PHP 5.2 -- and was able to run the Image 1.4 database upgrade successfully. I'm all set now, and also running on a better platform!

Thanks for all the help.

bomarmonk’s picture

bomarmonk commented

Any takers on patching this? I have a host who is stuck in the stone ages... and a sticky contractual situation with moving to another host. Any support would be appreciated.