I could not replicate this issue running 5.2.2. I consulted with a few members and the consensus was to try a newer version of the ORM, as it may have been fixed in 5.2.9 (#HHH-9663). If you are still having issues, could you possibly post more information on how I can replicate this?

Thanks!