Add translator_last_activity and reviewer_last_activity time columns #210
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.
Notion ticket link
Add translator_last_activity and reviewer_last_activity time columns to StoryTranslation model
Implementation description
translator_last_activity
andreviewer_last_activity
time columns to databaseSteps to test
docker exec -it planet-read_py-backend_1 /bin/bash -c "flask db upgrade"
translator_last_activity
andreviewer_last_activity
have been added to the tablesstory_translations
andstory_translations_all
a.
docker exec -it planet-read_db_1 /bin/bash
b.
mysql -u root -proot
c.
use planet-read
d.
select * from story_translations;
e.
select * from story_translations_all;
What should reviewers focus on?
Checklist
docker exec -it planet-read_py-backend_1 /bin/bash -c "black . && isort --profile black ."
and I have generated new migrations:flask db migrate -m "<your message>"