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 Voyage's boundaries. > - if one object can be on repo1 and repo2, then probably you need to join > those repositories This put me back at my initial questioning: is there any reason to have several repositories for one application domain? > - if that duplicated value is an enum type (like enum objects), then you do > not want to persist that: what you do is to persist a reference, then on > materialisation you refer to your enum (I do that a lot, in some apps)\ > - if you want to have for example, your list of organisations in one > repository and then one repository for each organisation, you can still apply > same pattern as before, but instead enums you persist a reference to your > organisation and then on materialisation you can repoint to it. Indeed, I was thinking about storing reference. Thanks Hilaire -- Dr. Geo http://drgeo.eu
