David Buchmann

Oh indeed, why not. Though not suitable for all cases, often you want a mixed tree - or you can go with orm right away. Could we offer to set...

good point about the prefetch helper. another thing could be when i ask for /parent/child to actually fetch /parent so that we have parent right away. this could get expensive...

on PHPCR level, there is https://github.com/phpcr/phpcr-utils/blob/master/src/PHPCR/Util/NodeHelper.php#L137 which accepts a name hint. it looks like we don't support this in the [auto strategy](https://github.com/doctrine/phpcr-odm/blob/master/lib/Doctrine/ODM/PHPCR/Id/AutoIdGenerator.php) that happens when you use the [auto strategy](http://docs.doctrine-project.org/projects/doctrine-phpcr-odm/en/latest/reference/basic-mapping.html#basicmapping-identifier-generation-strategies)....

isn't "AUTO" what we need, with a way to provide extra information for the name hint? the parameter that is now hardcoded to `''`?

ah i see. i think that this could end up being too specific logic. when looking at the child document, you don't know if you detected it by looking at...

i think the reason this is done before prePersist is so that listeners can use the id if they want to e.g. update related things. my usual question here is:...

having a good solution for the collection mapping would be great. fiddling with the events and order of events is very tricky, as the interaction is complicated and will lead...

we need to think through what the best solution is. we also discussed about storing hashmaps as nodes on and off. having too many different but very similar things could...

you mean we overlook when there are only translations to update and no other changes?

that would be something the orm does not do as its not aware of translations.