Script to add rows to notification_history table #2068
Merged
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
sastels
force-pushed
the
enlarge-db-script
branch
from
4b10949 to
bce1616
Compare
sastels
force-pushed
the
enlarge-db-script
branch
from
542dd58 to
535a5c0
Compare
|
I should add a README for this showing how to use it locally or from a k8s api pod. |
ben851
approved these changes
Jan 22, 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.
Summary | Résumé
Add new rows to notification_history table. This will be useful to make the dev / or staging database the same general size as production.
Test instructions | Instructions pour tester la modification
Open your local database in your favourite viewer and see the 2 new rows with client_reference "test2"