Good afternoon

When upgrading to 1.4, I receive the following errors:

user warning: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'EXISTS ( SELECT * FROM dru_files f2 WHERE f2.filepath = f1.file query: SELECT f1.fid, f1.nid, f1.filepath FROM dru_files f1 INNER JOIN dru_node n ON f1.nid = n.nid WHERE n.type = 'image' AND EXISTS ( SELECT * FROM dru_files f2 WHERE f2.filepath = f1.filepath AND f1.fid <> f2.fid AND f1.fid < f2.fid ) in /home/content/t/i/m/timatlee/html/d5/includes/database.mysql.inc on line 172.

As well, the update summary reports:

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

PHP Version 4.3.11
Client API version 5.0.18
Server version 4.0.27-max-log

The module still seems to work - but I haven't tested the module completely.

Comments

drewish’s picture

drewish commented

well that's a load of crap... looks like mysql 4.0 doesn't support EXISTS? I'll have to see if I can re-write that as an inner join...

drewish’s picture

drewish commented
Version: 5.x-1.3 » 5.x-1.4

oh, i should mention that that query failing shouldn't hurt anything. that update was designed to clean out duplicate records in the files table. hopefully you'll be able to help me test out a revised query.

timatlee’s picture

timatlee commented

Yeah, looks like it isn't affecting anything - Still creating image nodes, viewing at different sizes, all that good stuff.

I should be able to assist with testing any updates - I backed up the database before upgrading, so it's cake to restore it to the pre-upgrade point and try again.

drewish’s picture

drewish commented

eh, i'm considering just saying that mysql 4.0 is not supported... 4.1 is a much better release

drewish’s picture

drewish commented
Title: Problem upgrading to 1.4 » 1.4 update incompatible with MySQL 4.0

better title

nancydru’s picture

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

End of Product Lifecycle.
Active development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

http://dev.mysql.com/doc/refman/4.1/en/index.html

Ask your host to move to a supported version...

drewish’s picture

drewish commented
Status: Active » Closed (won't fix)

thanks nancyw, that was all the excuse i needed!

nancydru’s picture

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

Wish I could do that on my Site Documentation module. I had to fix it and it created a really UGLY Sql statement and two different sets of code.

drewish’s picture

drewish commented

marked http://drupal.org/node/160187 as a duplicate of this