A quick search for file_revisions or {file_revisions} reveals that there's only one match in image.module only:

    db_query("INSERT INTO {file_revisions} (fid, vid, description, list) VALUES (%d, %d, '%s', %d)",
             $fid, $node->vid, '', 0);

So in short, the module can not be working right, right?

Comments

Stuart Greenfield’s picture

Stuart Greenfield commented

I think I am having an issue as a result of this.

I am just setting up my first Drupal 4.7 site, migrating for 4.6. In doing some development work on my own modules I noticed that the {file_revisions} table seemed to be filling up. When an image is deleted the corresponding entries aren't removed from this table.

mr700’s picture

mr700 commented

Exactly my point, which makes me seriously wonder if someone is seriously using this module with 4.7 at all...

mr700’s picture

mr700 commented
Status: Active » Closed (fixed)

I don't use it on 4.7 and can't check if the issue is still here, but for 5.0 looks ok. If someone else cares - reopen.

drewish’s picture

drewish commented

whoops, didn't know there was an issue for this. i committed a patch for 5... if anyone cares, feel free to mark this as to be ported.