Andreas Braun

> Out of curiosity, what tool is reporting usage of `@internal` stuff? This looks like it's coming from the `DebugClassLoader` in Symfony, which checks the namespace on internal classes. This...

To elaborate on the last paragraph in the previous comment, you should always use collections internally. Allowing a `setChildren` call to replace the entire collection is bound to cause problems,...

I'm scheduling this for a fix in the next patch release. On a different note, I believe it may be worth deprecating this automatic type conversion. For a clean API,...

Quick update: this is currently waiting on https://github.com/mongodb/mongo-php-library/pull/599, which is most likely going to land in version 1.5.0 of `mongodb/mongodb`. There is `DocumentManager::CLIENT_TYPEMAP` which has to be used when manually...

Yes: we've decided to not implement a `Client::withOptions` helper in the MongoDB Driver, due to its implications on the underlying extensions. If you are creating your collections manually, you currently...

Yes - we've got some catching up on those. Current focus is on ODM 2.0, which will (finally) get rid of the legacy driver and thus allow us to start...

@malarzm I think we need to re-educate that bot...

Yes, that is the expected behavior at this time. We will not be changing this for 2.0 either.

@g13013 if you are not relying on `$setOnInsert`, then assigning an identifier when the entity is created will work to force an upsert. If you want to use `$setOnInsert`, you'll...

> By the way at the moment a workaround we are using is avoiding ReferenceOne-mappedBy and just using ReferenceMany-mappedBy instead, and practically ignoring any potentially found additional documents past index...