[BUG] First level .Include(...) doesnt matter about litedb

[ssteiner]

Did you look at what is contained in these children? With DbRef, if you do not do the Include, you'll still get the Object, but it contains just the Id, nothing more. Then, to set a child, you don't have to look up the child, you just instantiate a new child with the right Id and LiteDB figures out the rest.
LiteDb stores object type and Id of a DbRef - and auto-hydrates it - but it doesn't really read the child, it just instantiates the object and fills the Id, and that's it.

Yes if feels weird coming from EF (I took the same path), and I had to adapt my workflow a bit, but in the end, it's just one of those things that are different between SQL and NoSql. I've been working with MongoDB and RavenDB recently and they have their own different way of handling these things - they don't auto-hydrate but their way of handling DbRefs is in the end even more different from EF (and not in a good way imho).

[RedQueen87]

Great, I see now.
All Name properties are NULL when I don't use .Include(...).
And with .Include(...) it contains inserted string.
So now I am sure its not a bug but a feature :)
Thanks for explanation