Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Handle data drift #4

Open
spietras opened this issue Apr 4, 2022 · 0 comments
Open

Handle data drift #4

spietras opened this issue Apr 4, 2022 · 0 comments
Assignees
@spietras
Labels
feature New feature or request

Comments

@spietras
Copy link
Member

spietras commented Apr 4, 2022

Since there are two databases involved, it's harder to maintain integrity. emishows should be responsible for that. To some extent, it already is, if data changes flow only through it. But someone can (shouldn't but can) manually delete some data from one database and then there is an invalid state. emishows should handle that somehow. At least hide invalid data from users, at most handle integrity completely.
@spietras spietras added the feature New feature or request label Apr 4, 2022
@spietras spietras self-assigned this Apr 4, 2022
@spietras spietras moved this to TODO 📋 in shows Sep 2, 2022
@spietras spietras added this to shows Sep 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@spietras spietras

Labels
feature New feature or request
Projects
shows
Status: TODO 📋
Milestone
No milestone
Development

No branches or pull requests
1 participant
@spietras