Update database before content store #583
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
paulrobertlloyd
added
enhancement
paulrobertlloyd
force-pushed
the
575-database-file-sync
branch
4 times, most recently
from
a9e2303 to
c178b8e
Compare
paulrobertlloyd
force-pushed
the
575-database-file-sync
branch
from
c178b8e to
a1344bc
Compare
4 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.
Currently:
This means data creation/manipulation is happening in two places. It also means content gets uploaded before the database has been queried, so if a database operation fails, the 2 fall out of sync.
This PR updates the media and Micropub endpoints so that post/media items are created/updated, and the database operation occurs before any file is published or uploaded.