Implement the EF licensing data store - #5714
Open
johnsimons wants to merge 1 commit into
Open
Conversation
RavenDB stored throughput as an incremental time series keyed by a case-insensitive document id. The relational equivalent is a row per endpoint per day, with lowercased name columns to keep endpoint identity and sanitized name matching case-insensitive on PostgreSQL. Recording adds to the day's total via ExecuteUpdate so concurrent writers queue on the row rather than overwriting each other, and the four singleton documents share the Settings table.
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
1 participant
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.
RavenDB stored throughput as an incremental time series keyed by a case-insensitive document id. The relational equivalent is a row per endpoint per day, with lowercased name columns to keep endpoint identity and sanitized name matching case-insensitive on PostgreSQL. Recording adds to the day's total via ExecuteUpdate so concurrent writers queue on the row rather than overwriting each other, and the four singleton documents share the Settings table.