Hi,

I have three questions regarding these two options.
As a matter of analogy to what I know, for me a Voyage repo is like a
database and collections like tables in relational db world.

So what is the argument to use multiple repo for an application domain?

When using two repo A and B, is it ok to have instances saved in A with
attributes saved in B?
When fetching instances from A, will these instances get their
attributes saved in B right?

Thanks

Hilaire

-- 
Dr. Geo
http://drgeo.eu


Reply via email to