21 Mar
2020
21 Mar
'20
9:35 a.m.
On Mar 21, 2020, at 6:23 AM, Geaaru <geaaru@gmail.com> wrote:
I think that the fix must be a little more complex.
Possibly. It's also possible to just document this limitation as "don't do that".
The best solution probably is this: - try to identify the target MongoDB Server version on first connection and store this inside mongo db instance struct - to change the code in the way that if mongodb is >= 4.2 update is handled as an array instead of a single document.
Obviously, this introduces complexity in the code.
Or just documentation is "don't do that" :) Alan DeKok.