David Buchmann
David Buchmann
would be great to have a test case for this situation, whether its currently broken or not.
agreed. was there a test case i did not find? or can you do one?
i agree. we had endless discussions in #262 about automatically merging / replacing documents. for an explicit replace operation, there are already many options: either replace just the document itself...
the problem with remove & persist new is that all children of the old document are removed as well. when this is intended, it can make sense to do this...
it looks like we added some sanity check in the query builder that is not really right. semantically that code looks wrong, it should be 'content' => $content and the...
oh, one thing: who is the owning side? i think searching by referrer would be difficult. searching for a field referencing something else should be possible.
https://github.com/symfony-cmf/MenuBundle/pull/241 looks right but seems not to work. wouter, can you maybe try to write a failing functional test here in phpcr-odm for this that shows the problem?
see https://github.com/doctrine/DoctrinePHPCRBundle/issues/179 for previous discussion
are you using 1.2.0-RC1? @lsmith77 did a refactoring of the changeset calculation to clean up things. what you report sounds like a regression. does the problem occur with 1.1 as...
i think we should aim for the same behaviour as the orm. if the orm does not do this, its a good reason for me to not do it here...