Nevertheless we need to compute changesets, otherwise the entity is not persisted. Calling persist on flush does not do the trick. What about that, Marco? Any suggestion how to handle that wirhout calling internals?
Meanwhile we found, that even the doctrine manual encoreges us to use those functions. Little bit confusing, as both are considered to be internal and recomputeEntityChangeSet() is even ignored by api documentor. Not to mention, that PhpStorm strikes through any use of computeChangeSet() as it is marked as internal by annotation. How to deal with that, Marco? -- You received this message because you are subscribed to the Google Groups "doctrine-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/doctrine-user. For more options, visit https://groups.google.com/d/optout.
