April 30, 2017
9:27 a.m.
On 30. Apr 2017, at 11:18, Mark Rizun <mrizun@gmail.com> wrote:
Sorry, I wasn't very accurate in previous email. Actually, my friend is using MongoTalk/Voyage, and she encountered a problem that it is not possible to work with databases created in 3.0+ versions of MongoDB. Probably this issue is related to new storage types (connection part is fine).
I am running a Pharo3.0 image (with an older Voyage) against MongoDB 3.2. I think I am already using "WiredTiger" as database. If you can reproduce it, we can have a look. The only issue I have seen is Sabines authentication failure with more "modern" schemes. holger