Skip to content

[api] file check should be against attachmentsource SHA256sum, not hashsum of converted file #2328

@madduck

Description

@madduck

If during upload, a file is converted/modified, it will yield a new SHA256sum (see #2327). If the same file is uploaded again, the conversion/modification will likely produce a completely new file with a different SHA256sum (because of timestamps in the generated PDF etc.). Therefore, even with skipDuplicates in metadata, certain duplicates cannot be prevented in the status quo.

The original SHA256sum is kept in the table filemeta. It should be used instead of the hashsum of the converted file.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions