Can we possibly get something like #353458: hook_file_references() was not designed for a highly flexible field storage for D6? This is especially useful to make it retrievable by views.

Comments

scroogie’s picture

scroogie commented

I'll wait until the original patch hits core (which it hopefully will) before backporting, but I'd like to hear an opinion first. I think this would be very helpful as every module could count the file usages with one query, instead of calling a hook.

quicksketch’s picture

quicksketch
he/him
commented

I don't anticipate adding this feature. If the core version gets in, maybe, but I still doubt it. It would be a very clear dividing line between modules that support FileField 3.x and FileField 4.x in Drupal 6. You can still do everything even without the single file references table, it just is a lot less efficient since you have to query every file field on the site as we do now. I think adding a new version of FileField would cause a lot hassle with our end users, since it's likely that other modules would only support 3.x OR 4.x. Meaning that users get frustrated when they're using modules that require 3.x but then want one module that has 4.x, and none of the other modules have been ported.

I think #353458: hook_file_references() was not designed for a highly flexible field storage is a great idea, but I don't think it's worth creating a new branch of FileField for it.

scroogie’s picture

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

Okay, I see your point.