WIP: Move Repliear to row versioning #163
Draft
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
1. update cve table inside postgres 2. generate patch by selecting from cve
aboodman
force-pushed
the
aa/row-versioning
branch
from
f542ef7 to
47f024c
Compare
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.
This PR picks up from @tantaman's. There were a lot of little things I wanted to try and easier to build on and use code than go back and forth in reviews.
The main idea in here so far is to change the approach to calculating the pull in a way that for me at least simplifies thinking about it. There are now two steps that run on every pull, regardless of input:
client_view_entry. This can be done entirely in the DB without round-tripping through application.