Skip to content
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

Duplicate DB entries in filecache table when renaming folder in WebUI #2 #3388

Merged
merged 2 commits into from
May 25, 2013
Merged

Duplicate DB entries in filecache table when renaming folder in WebUI #2 #3388

merged 2 commits into from
May 25, 2013

Conversation

roha4000
Copy link

I previously sent a Pull Request concerning this Bug but screwed up the commit because I just copied the changes I made on the 5.0.5 TAG to the trunk. Well, that did not work out.

Now this one passes the unit tests. I also added some additional tests to ensure that another users cache entries are not Updated. Hope this one will do it :-)

To reproduce the Bug you need two users having the same folder structure. The folders must contain at least one file. Now rename one folder and all filecache entries with the same path will be updated with the new folder name ... regardless of the storage id.

@MTGap
Copy link
Contributor

MTGap commented May 16, 2013

Doesn't look like Jenkins failed specifically because of your commits. @DeepDiver1975 Can you investigate?

Looks good now @roha4000 and thanks for the tests. Could you take a look at http://owncloud.org/about/contributor-agreement/

@DeepDiver1975
Copy link
Member

Doesn't look like Jenkins failed specifically because of your commits

aaargh - yes phpunit is seg faulting
not related to this pr

@roha4000
Copy link
Author

I've just send the signed agreement to Frank.

@karlitschek
Copy link
Contributor

got it. Ready for merge if reviewed.

@DeepDiver1975
Copy link
Member

@owncloud-bot retest this please

@roha4000
Copy link
Author

Seems that phpunit is still segfaulting.

@DeepDiver1975
Copy link
Member

Seems that phpunit is still segfaulting.

yeah - related to some issue within the clover report generation

@roha4000
Copy link
Author

Well, I'm not sure how to proceed. Can I just merge the pr or shall I wait for the test to be restartet and / or a review?

@DeepDiver1975
Copy link
Member

@roha4000 our review process requires two people giving a +1 before you can merge any pr.

Maybe I'll have a look tonight.

@icewind1991 can you have a look as well

@butonic
Copy link
Member

butonic commented May 21, 2013

@roha4000 rebase please

@MTGap
Copy link
Contributor

MTGap commented May 22, 2013

Something went wrong with that rebase. What did you do?

Roland Hager added 2 commits May 22, 2013 08:18
… move(). Add storage id to the where clause to avoid updating entries of other users.
…ntries

Added a second storage and cache Object to simulate a second user.
@roha4000
Copy link
Author

Yeah, something went wrong :-). I've tried to get rid of the Merge Commit after rebasing to the upstream ... anyway it should be OK now.

@roha4000
Copy link
Author

I rebased as requested. Could someone invest some time to review this two lines of changed code and the adapted unit test please?

@icewind1991
Copy link
Contributor

👍 Looks good

@MTGap
Copy link
Contributor

MTGap commented May 25, 2013

Now we're good 👍

MTGap pushed a commit that referenced this pull request May 25, 2013
Duplicate DB entries in filecache table when renaming folder in WebUI #2
@MTGap MTGap merged commit 0fdf3a7 into owncloud:master May 25, 2013
@MTGap
Copy link
Contributor

MTGap commented May 25, 2013

Backport: 07fb230

@lock lock bot locked as resolved and limited conversation to collaborators Aug 20, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants