Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Fail fast if two ApolloStores use the same underlying database #3564

Open
Tracked by #2331
martinbonnin opened this issue Nov 17, 2021 · 0 comments
Open
Tracked by #2331

Fail fast if two ApolloStores use the same underlying database #3564

martinbonnin opened this issue Nov 17, 2021 · 0 comments
Labels
🗄️ Normalized cache ✨ Type: Feature

Comments

@martinbonnin
Copy link
Contributor

Because the database lock belongs to ApolloStore, using two ApolloStore (and therefore two locks) can lead to Concurrent modification exceptions.

We could catch those cases early to give better diagnostics.
@martinbonnin martinbonnin changed the title Fail fast if to ApolloStore use the same underlying database Fail fast if two ApolloStores use the same underlying database May 17, 2024
@martinbonnin martinbonnin mentioned this issue May 17, 2024
Open
41 tasks
@BoD BoD mentioned this issue Dec 13, 2024
Open
@BoD BoD changed the title Fail fast if two ApolloStores use the same underlying database Fail fast if two ApolloStores use the same underlying database Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🗄️ Normalized cache ✨ Type: Feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@martinbonnin