foundationinstance, a foundation in where everything is configured, from which the
Loader. Because Legacy Type Mapping affects loading, it has to go in there.
InquiringLegacyTypeMappingResultor) there are a few settings: When should he ask? Always or only if something is unclear. Never does not make any sense of course, then you shouldn't use it, or alternatively the printing resultor.
pinare too different to be automatically assigned to each other. Therefore, it is wrongly assumed that
customeridis omitted and
commerceIdare surprisingly similar (75%) and are therefore assigned. But that's not what we want.
customeridwould be eliminated by the implicit decision. This is too delicate not to inquire, so it is always necessary to ask.
customeridis now called
commentshould be omitted
pin, the similarity does not matter, it is the mapping that matters. To indicate this, it says "[mapped]" instead of the similarity. The rest is as usual. Only comment is now "[discarded]", according to the mapping. The difference to the above is namely: This is an explicitly predetermined absence. That does not force inquiry.
lastNameis below the required "minimum similarity", so rather ask.
commentexample above: is 75% similar to
commerceId. Still wrong. Then prefer 80%? Or 90%? Of course it is better, but the danger is still there.