Filefield only insert/update file records in {files} and totally bypass {file_revisions}. This creates problem with other file related modules such as upload, media_mover, which are hard to trace.
Of course don't forget to handle deletion as well. (#292151: Files are not deleted when replaced)

Side note: on quick glance, imagefield seems to have the same issue.

Comments

jpetso’s picture

jpetso commented
Status: Active » Closed (works as designed)

Invalid, this is by design. Filefield for Drupal 5 does not mess with {file_revisions} because it's upload.module's private table. (For that reason, it has been renamed {upload} in Drupal 6.) Previous attempts at filling the {file_revisions} table were unsuccessful and hackish because upload.module does not offer the necessary flexibility to allow the co-existence of two modules in that table. Imagefield has the same rationale.

If media_mover depends on files to exist in {file_revisions}, that is a bug in media_mover. If any problems with upload.module occur, please go into detail what does not work. (On the other hand, Filefield 5.x development is pretty much dead so there probably won't be any changes anyways.)