Mergable persistance in Postgres tabular #246
Open
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
|
So I think we definitely need to crack this! I want to make sure we are capturing the full CRDT behavior though, not just row-level. CRDT hashes occur per value, per cell, per row, per table, and for all values and for all tables. We would need at least one 'tinybase' table to capture all of these. Otherwise I would need to get very comfortable that row-level hashes only were good enough to resuscitate the data in a way that was robust enough to withstand the scrutiny of a full sync sequence. (In any case, we also face the challenge of folks updating data through some other client and not having the CRDTs & hashes updated accordingly. What do you think? |
jamesgpearce
force-pushed
the
beta
branch
2 times, most recently
from
73d01b3 to
abb4687
Compare
|
(Do we want to keep these now you have your dedicated connector?) |
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.
Summary
Implements #237 to support merging updates from postgres to mergeable store.
How did you test this change?
WIP
WIP status
I'm still working through this feature and it needs more testing. But the existing code should outline intended solution.