[TECH] ajoute une contrainte d'unicité pour campaignParticipationId
sur knowledge-element-snapshot
(pix-17358)
#11964
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🌸 Problème
Il existe des fois où un snashot peut être créer 2 fois pour la même participation.
🌳 Proposition
On ajoute une contrainte d'unicité pour éviter cela
🐝 Remarques
Cette contrainte a été déjà ajouté en prod, d’où la vérification de son existance dans le up
🤧 Pour tester
npm run db:rollback:latest
pour supprimer la contraintenode src/prescription/scripts/add-unicity-constraint-knwoledge-element-snapshots.js --dryRun false
npm run db:migrate
pour jouer la contrainte