Oban like migration system #1
Merged
Conversation
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
This commit introduces an Oban like migration system for the ErrorTracker. Users can generate their own migrations that call the ErrorTracker migrations and possibly set an alternative database prefix in case that they want to store the errors in a separate schema than the rest of the application. This commit also updates the dev script to showcase how to use the new migration system on an alternative prefix.
odarriba
reviewed
Jun 5, 2024
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.
This commit introduces an Oban like migration system for the ErrorTracker. Users can generate their own migrations that call the ErrorTracker migrations and possibly set an alternative database prefix in case that they want to store the errors in a separate schema than the rest of the application.
This commit also updates the dev script to showcase how to use the new migration system on an alternative prefix.
Keeping track of the current schema version is not an easy task as we cannot rely on the regular
schema_migrationstable that Ecto creates. Instead I've followed Oban steps and recorded the current schema version in the table description.This is read before running the migrations and updated after, so subsequent migrations can know which version to start from.