Amélioration des contraintes foreign de la table arête_personne__cap_écriture_annotation #87
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…écriture_annotation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
En essayant de re-générer un code_accès par email, la base de donnée refusait de modifier le code_accès, parce que ça transgressait la contrainte
foreigndearête_personne__cap_écriture_annotation.personne_capCette PR rajoute surtout un
.onUpdate('CASCADE')à cette colonne pour que quand le code change, la colonnearête_personne__cap_écriture_annotation.personne_capest modifiée avec la nouvelle valeur