Situation looks a bit clearer. The duplicated object entries issue arises with two concomitant situations:
- the object reimplements hash and = methods - one of the attributes participating in the comparing protocol is modified. In that scenario, Voyage guess it is dealing with a new element, even if it is not the case. In some scenario, user really needs to override the comparing protocol, how to deal with the duplicated entries issue in that case? Hilaire Le 05/03/2017 à 10:19, Hilaire a écrit : > I must stress the same instance duplication occurs when I inspect an > instance, edit one attribute from the inspector, then save it from the > inspector with "self save" command. -- Dr. Geo http://drgeo.eu
