Open
Conversation
Once the backend data is present, it can be added simply by calling liquibase generateChangeLog --username $DB_USER --password $DB_PASSWORD --url jdbc:postgresql://localhost:5432/postgres --changeLogFile src/main/resources/db/changelog/changelog-1.0.sql
Aaron2000119
approved these changes
Mar 9, 2023
|
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.
In the future, any PR that changes stored data must also adapt the corresponding changelog under
src/main/resources/db/changelog/changelog-<version>.sql.New versions should also use a new changelog instead of appending to an old one.
For details on how to keep the changelog up to date, consult the docs.
The initial changelog was not generated as there is no data yet.
Once it is present, it can be added simply by calling
Part of Gamify-IT/issues#439.