hm, not sure. i don't think that is the problem we talked about, but also an interesting question. we could detect that a lot earlier, right in loadTranslation, if we request the document in the locale it already is. not sure what should happen at this point - either we could simply ignore the request, or refresh from the database / memory cache. but that would be redundant of refresh (or is that called reset?) i think, so maybe not a good situation.

but the problem i think we talked about is when doing bindTranslation. if during bind, we detect that the document currently is in a different locale than the one its asked to be bound to, and the target already exists (locally or in storage), there is something wrong.   for this, it does not matter whether the translation is already in this cache or not.