Thanks Esteban for your detailed answer.
Le 23/02/2017 à 13:23, Esteban Lorenzano a écrit :
> Voyage will not handle that kind of problem. Voyage will not know
anything about instance A being saved in repo1 AND repo2.
> Also, I do not think it should :)
Thanks to clarify, it helps to understand
Hi Hilaire,
Voyage will not handle that kind of problem. Voyage will not know anything
about instance A being saved in repo1 AND repo2.
Also, I do not think it should :)
I think you have a design problem if you want something like that to work…
let’s explore the consequence of implementing som
Hi,
It looks like Voyage will duplicate in repo A the instance saved in repo
B in the first place. These two instances of an identical object will
have different ID.
The following script shows this behaviour:
| orga repo1 repo2|
repo1 := VOMongoRepository host: 'localhost' database: 'test1'.
rep
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
