Handle empty DB while expiring versions #36556
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
artonge
added
26-feedback
bug
feature: versions
php
artonge
force-pushed
the
artonge/fix/expiring_file_versions_empty_db
branch
2 times, most recently
from
633712a to
0dd8c91
Compare
artonge
changed the title
9 tasks
|
/rebase |
artonge
requested review from
a team,
ArtificialOwl,
blizzz and
icewind1991
and removed request for
a team
Version on the FS can have no equivalent in the DB if they were created before the version naming feature. This makes sure that we catch the resulting exception and proceed as usual. Fix #36541 Signed-off-by: Louis Chemineau <louis@chmn.me>
nextcloud-command
force-pushed
the
artonge/fix/expiring_file_versions_empty_db
branch
from
0dd8c91 to
21cd3b0
Compare
blizzz
approved these changes
Feb 16, 2023
Merged
9 tasks
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.
Version on the FS can have no equivalent in the DB if they were created before the version naming feature. This makes sure that we catch the resulting exception and proceed as usual.
Fix #36541