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

populate functionality to be consistent with push/set #1306

Closed
zbenmo opened this issue Jan 21, 2013 · 1 comment
Closed

populate functionality to be consistent with push/set #1306

zbenmo opened this issue Jan 21, 2013 · 1 comment

Comments

@zbenmo
Copy link

zbenmo commented Jan 21, 2013

I find the populate functionality very useful. You store in the database object ids, yet you need the actual documents so you just ask for them and instead of ids you have the objects.

But, the same is needed for push/set. You set an object and a moment later only the id is there. You don't have any more the object (at least associated with the main document).

I recommend that the duality be exposed explicitly, and be consistent all the way at all times. This will make the push/set/populate functionality truly useful and consistent.

With kind regards, Oren.

@aheckmann
Copy link
Collaborator

duplicate of #570 and fixed in 3.6x branch.

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

2 participants