Repository navigation
cotisation: migration de vieilles valeurs de type_reglement en bdd - #2427
Merged
Merged
Conversation
Mopolo
approved these changes
Oct 6, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Signalé sur Slack : https://afup.slack.com/archives/C03L64VE9/p1790926334339729
Problème
Une cotisation en production a
type_reglement = 9. Doctrine ne peut pas hydrater l'entitéCotisationLa valeur 9 correspond, au mieux, à une valeur de l'autoqualifier :
Aucun code, actuel ou passé, n'a jamais écrit cette valeur : les constantes legacy comme l'enum vont de 0 à 4. La donnée a sans doute été modifiée directement en base. L'erreur apparaît depuis le passage à Doctrine, qui valide l'enum.
Correctif
Migration qui passe à
3(Autre) toutes les valeurs hors enum