Add updated_at field to stash_id's #5259
Open
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
|
|
ikmckenz
force-pushed
the
updated-at
branch
2 times, most recently
from
18e940d
to
8f750e0
Compare
ikmckenz
force-pushed
the
updated-at
branch
from
8f750e0
to
aea0b8f
Compare
|
Rebased on latest develop and bumped the schema version |
Stored as a time (not OptionalTime), and so on migration set all existing StashIDs to have time zero, then on scrape update.
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.
Stored as a time (not OptionalTime), and so on migration set all existing StashIDs to have time zero, then update on scrape, tagger, etc.
First and biggest part of #3553 , only thing left would be displaying, and maybe a task to update things older than X.