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

Overlapping child documents are not published to all their named collections #17

Closed
bastiaanterhorst opened this issue Oct 31, 2014 · 1 comment
Closed

Overlapping child documents are not published to all their named collections #17

bastiaanterhorst opened this issue Oct 31, 2014 · 1 comment

Comments

@bastiaanterhorst
Copy link

When creating multiple child collections that have a collectionName (so they end up in virtual collections), overlapping documents (docs that should appear in both virtual collections) only appear in one of the virtual child collections.

This is not an issue when you're not using the collectionName, since they you're always finding in the real mongo collection, and everything will be present there.
@reywood reywood changed the title Overlapping child collections are not published to all their named collections Overlapping child documents are not published to all their named collections Nov 4, 2014
reywood added a commit that referenced this issue Nov 4, 2014
@reywood
Fix issue #17, docs are not published to both primary collection and …
eeaa66e 
…alternate collection when they overlap
@reywood
Copy link
Collaborator

reywood commented Nov 4, 2014

Thanks for finding and reporting this. Should be fixed now.

@reywood reywood closed this as completed Nov 4, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bastiaanterhorst @reywood