TYPO3 Core

Use case: I have a database table where PDF files get attached to records by an automated process. The IRRE/FAL field to which such records are attached is set as read-only. The project uses workspaces and when a new version is created, a copy of all sys_file_reference entries is also created. Upon publication, 2 problems may occur:

1. the user has the rights to the sys_file_reference table. Even if nothing has changed, the "tstamp" field of the sys_file_reference entries are updated, which is not desirable, since we want to keep the date at which the automated process attached the file to the record.
2. when the user does not have the rights to the sys_file_reference table, the problem gets worse: when the parent record is published, the children are left ignored. They may then appear in some other user's workspace view, when that use has the rights to the sys_file_reference table, but they are then "detached" from their parent record.

I tried to have the field ignored in workspaces by using a display condition like VERSION:IS:false, but this has no effect on children relations.

Unfortunately, I don't have the time to fully dig into this issue to try and submit a patch. For now, I will use one of the DataHandler hooks to clean up the mess, but I think it would be really correct to ignore dependencies when a field is excluded from workspaces (and AFAIK the display condition is the only way to exclude a field from the versioning process).