Normalisation nom base de données pour simplifier les restore #148
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
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.
... bon, c'était pas ce sur quoi je bossais, mais ça a eu lieu comme ça...
j'ai eu un problème de BDD sur ma machine
Les restore échouaient, donc, j'ai travaillé à une procédure de restore fiable
Ça m'a demandé de nommer la BDD en dev comme celle en prod
@Ynote J'imagine que si tu merges, tu vas perdre le contact vers tes données (vu que le nom de la BDD a changé), donc le test ici, c'est de refaire un restore et vérifier que ce qui s'affiche chez toi est à peu près la même chose que la prod
et vu qu'on n'a pas vraiment changé quoi que ce soit de notre côté, j'imagine que c'est des différences dans le format de dump de Scalingo