Skip to content
This repository has been archived by the owner on Feb 22, 2020. It is now read-only.

Referencing external documents, opposed to embedding. #38

Open
AlBakerKY opened this issue Jul 28, 2016 · 3 comments
Open

Referencing external documents, opposed to embedding. #38

AlBakerKY opened this issue Jul 28, 2016 · 3 comments
Assignees
Labels

Comments

@AlBakerKY
Copy link

AlBakerKY commented Jul 28, 2016

If I want to store document references instead of embedded documents, how would I best achieve that in the repo? For example, I want to have users that can share newspapers..so something like this, where people can keep references to their favorite newspapers.

class Newspaper:Entity { string Name; string Content; Data publishDate} 
class User:Entity { string LastName; List<Newspaper>newspapers; } 

But internally that List should be serialized to store references to newspapers inside user, not content.

How seamlessly can that be accomplished and should I manually be maintaining those references through in my derived repositories?

Should those references be through ObjectIDs or strings?

Thanks for any help.

Al

@RobThree
Copy link
Owner

Let me know if #15 helps you answer your question.

As to answer your "How seamlessly"; that depends on what your definition of seamless is I guess 😉

@RobThree RobThree self-assigned this Jul 28, 2016
@AlBakerKY
Copy link
Author

#15 does help, thank you. As far as storing references, should they be strings or objectIDs?

@RobThree
Copy link
Owner

It's up to you; nothing stopping you from using either way 😉

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

No branches or pull requests

2 participants