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.

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

Support syncing only parts of the Supabase table (similar to Firestore subcollections) #4

Open
marceljuenemann opened this issue Apr 3, 2023 · 0 comments

Comments

@marceljuenemann
Copy link
Owner

Both the one-off and realtime pull handlers could add WHERE clauses to only fetch a subset of the table. The important restriction on the WHERE clause here would be that rows must never leave that "partition" of the table, otherwise the pull handler wouldn't get notified about that "deletion".

This would basically enable subcollections like in Firestore. To implement this safely, the ID of the subcollection wouldn't actually be part of the RxDB, but rather the user would create one RxDB per subcollection they want to track and then pass that ID to SupabaseReplication.

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

No branches or pull requests

1 participant