-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixed move bug #163
Fixed move bug #163
Conversation
I found the same bug: #158 |
i merged #165 - @dantleech can you add a test about a child of the moved node and then call the method i added to transport to invalidate the cache and see if that fixes the problem? |
this might be related to jackalope/jackalope#191 |
@dantleech can you check if jackalope/jackalope#200 matters for this or not? |
needs a rebase |
The UUID of a node is indexed by the nodes path. This commit fixes an issue where this index is not removed, making the transport believe that there is still a node existing at this path.
- Added child test - Really bizzare -- why does the child rename based on the parent?
Updated. I added a test for the child - but something very strange happens, as in the test case:
Now the following path is in the database: |
maybe this is a bug in how we replace? |
ah, interesting. anybody on it right now or shall i have a look? |
I'm working all day so feel free :) |
continued in #168 - thanks lukas, your tip made it simple to fix. |
btw, i quickly checked if we might have a similar problem in phpcr-odm, but we only use str_replace in places where it makes sense. |
The UUID of a node is indexed by the nodes path. This commit fixes
an issue where this index is not removed, making the transport believe
that there is still a node existing at this path.