Skip to content
This repository has been archived by the owner on Feb 8, 2018. It is now read-only.

implement view materialization for teams #2282

Closed
chadwhitacre opened this issue Apr 14, 2014 · 2 comments
Closed

implement view materialization for teams #2282

chadwhitacre opened this issue Apr 14, 2014 · 2 comments

Comments

@chadwhitacre
Copy link
Contributor

Over on #1549 we've discussed view materialization. I propose that we try it out to gain experience with the technique. I think team memberships would be a good place to explore this pattern because the team memberships page is known to be super slow (#1417) and it's fairly isolated from the rest of the schema.

chadwhitacre added a commit that referenced this issue Apr 15, 2014
`memberships` was a bad name for this table because it's ambiguous with
community memberships. Renaming to `takes` fits the usage we've arrived
at and is parallel to `tips`. Tips and takes! Membership is then an
emergent property of data recorded in the takes table.
@chadwhitacre
Copy link
Contributor Author

I've submitted a PR to rename memberships to takes as a precursor to working on this issue. However, after looking at #1417 I believe that materializing (what is now) the current_takes view is not what is needed to speed up the members listing.

chadwhitacre added a commit that referenced this issue Apr 17, 2014
`memberships` was a bad name for this table because it's ambiguous with
community memberships. Renaming to `takes` fits the usage we've arrived
at and is parallel to `tips`. Tips and takes! Membership is then an
emergent property of data recorded in the takes table.
@chadwhitacre
Copy link
Contributor Author

Noise.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant