Migrate company caching to ID-based deduplicated keyspace - #53
Merged
Merged
Conversation
dontlaugh
marked this pull request as ready for review
February 12, 2026 16:18
bpapillon
reviewed
Feb 17, 2026
bpapillon
left a comment
bpapillon
left a comment
Contributor
There was a problem hiding this comment.
Plan here is to get clients (Schematic/Go and Airia/C#) updated before they update to this version of the replicator?
cbrady
reviewed
Feb 17, 2026
Instead of storing the full company JSON at every lookup key, lookup keys now store just the company ID string and a single ID-based primary key stores the full company. The full company data structure is only stored in one place.
schematic:company:{version}:{companyID}
dontlaugh
force-pushed
the
caching-updates
branch
from
February 17, 2026 16:38
c0c9c4d to
063485c
Compare
cbrady
reviewed
Feb 17, 2026
Pass p.pattern instead of constructing a new pattern inline.
cbrady
approved these changes
Feb 20, 2026
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
3 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.
Instead of storing the full company JSON at every lookup key, lookup
keys now store just the company ID string and a single ID-based
primary key stores the full company. The full company data structure
is only stored in one place.