optimized members materialized view #803
Merged
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
epipav
approved these changes
Apr 24, 2023
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.
Changes proposed ✍️
What
🤖 Generated by Copilot at 804aaa8
This pull request updates the database schema and the memberActivityAggregatesMVs materialized view to support multiple usernames per member per platform and to optimize the performance and storage of the member data. It renames and drops some columns, changes some constraints and default values, and modifies the query logic for the materialized view. The changes are implemented in two migration files:
U1682340963__optimized-members-mv.sqlandV1682340963__optimized-members-mv.sql.
🤖 Generated by Copilot at 804aaa8
Why
How
🤖 Generated by Copilot at 804aaa8
Checklist ✅
Feature,Improvement, orBug.Add screehshots to the PR description for relevant FE changesNew backend functionality has been unit-tested.API documentation has been updated (if necessary) (see docs on API documentation).