fix: resolve #72 - #280
Open
Shaidyk wants to merge 1 commit into
Open
Conversation
…ternal source with
6 tasks
RudraMalvankar
left a comment
RudraMalvankar
left a comment
There was a problem hiding this comment.
Nice work on the replication plugin! One question: how does this handle updates or deletes in the source database after a row has already been replicated? Since replication appears to be append-only, it seems those changes wouldn't propagate. Would it be worth mentioning this limitation more explicitly in the README so users know it's intended behavior?
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Resolves #72.
Added a new
ReplicationPlugin(plugins/replication/) that pulls data from the configured external data source (Postgres/MySQL/SQLite/Hyperdrive) into the internal Durable Object SQLite database, so a StarbaseDB instance can serve as a close-to-edge replica. Replication is pull-based and append-only: per table the user defines a tracking column (e.g.idorcreated_at), and each pull fetches only rows newer than the last checkpoint, which is persisted in atmp_replication_checkpointstable./claim #72