Skip to content

Don't double save Query Data #767

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 5, 2019
Merged

Conversation

schmidt-sebastian
Copy link
Contributor

This removes the sophisticated logic to determine whether we need to persist query data in releaseQuery() as LRU GC bumps the sequence number and always persists the query when the reference is removed.

@schmidt-sebastian
Copy link
Contributor Author

Screen Shot 2019-09-05 at 10 23 28 AM

I DID IT!

Copy link
Contributor

@wilhuff wilhuff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@wilhuff wilhuff assigned schmidt-sebastian and unassigned wilhuff Sep 5, 2019
@schmidt-sebastian schmidt-sebastian merged commit 8003a69 into master Sep 5, 2019
@schmidt-sebastian schmidt-sebastian deleted the mrschmidt/dontdoublesave branch September 5, 2019 22:40
schmidt-sebastian added a commit that referenced this pull request Sep 13, 2019
schmidt-sebastian added a commit that referenced this pull request Sep 13, 2019
@firebase firebase locked and limited conversation to collaborators Oct 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants