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'.
repo2 := VOMongoRepository host: 'localhost' database: 'test2'.
orga := 'Pharo' -> 13.
repo1 save: orga.
repo2 save: ('Hilaire' -> orga).
repo2 selectAll: Association.
=> an OrderedCollection('Hilaire'->'Pharo'->13 'Pharo'->13)
How do you guys avoid such duplication of identical instances in two
different repo?
Let's say you want to have in one repository a collection of reference
data, but these data are used by other instanced saved in another repo.
Then from time to time this data may need to be edited, copy of these
data will then be obsolete.
Thanks
Hilaire
Le 20/02/2017 à 19:26, Hilaire a écrit :
> 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?
--
Dr. Geo
http://drgeo.eu
