You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 11, 2021. It is now read-only.
the diff column is not the regular diff, rather some serialization of a structure that tells us what are new lines (+), deleted lines (-), or unchanged (|). Maybe a string with a length that matches the source file:
One reason to store the diffs is if the logic that collects all the new diffs is separate from the logic that serially applies them to the files between the known revision and target revision.
Caching the diffs may be useful, at the very least knowing what files are touched by what revisions will help us store a sparse table of tuids:
the
diff
column is not the regular diff, rather some serialization of a structure that tells us what are new lines (+
), deleted lines (-
), or unchanged (|
). Maybe a string with a length that matches the source file:or a run-length-encoded version of the same
or something smarter.
Even so, this
diff
may not be needed since it should have been applied to the subsequent changeset, and stored in thetuid
table already.The text was updated successfully, but these errors were encountered: