Add DB migration to delete orphaned tokens #8511
Merged
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 should be merged after #8510 (which will make sure that we don't orphan any more tokens).
Checking what the SQLAlchemy query evaluates to:
Testing
devdata_user
, go to http://localhost:5000/account/developer, and generate a tokendevdata_admin
, go to http://localhost:5000/account/developer, and generate a token, then go to http://localhost:5000/admin/users and deletedevdata_user
At this point you should have two rows in the
token
table in your DB: one belonging todevdata_admin
and one orphaned row belonging todevdata_user
.If you now run:
you should see
Deleted 1 orphaned tokens
and thedevdata_user
token should be deleted from your DB.