Implemented unique constraints in the file history model.
Added an integrity exception handler for creating entities.
Why
To establish a safeguard in the file history model against duplicate entries during concurrent workflow execution.
How
Introduced unique constraints with the combination of workflow and cache key (file hash).
Can this PR break any existing features. If yes, please list possible items. If no, please explain why. (PS: Admins do not merge the PR without this section filled)
No, the PR introduces unique constraints and handles integrity errors.
Database Migrations
Yes. file_history model
Env Config
Relevant Docs
-
Related Issues or PRs
-
Dependencies Versions
-
Notes on Testing
Screenshots
Checklist
I have read and understood the [Contribution Guidelines]().
What
Why
How
Can this PR break any existing features. If yes, please list possible items. If no, please explain why. (PS: Admins do not merge the PR without this section filled)
Database Migrations
Env Config
Relevant Docs
-
Related Issues or PRs
-
Dependencies Versions
-
Notes on Testing
Screenshots
Checklist
I have read and understood the [Contribution Guidelines]().