Details
-
Improvement
-
Resolution: Fixed
-
Major
-
8.4.3
-
Unit, Integration
-
Unknown
-
N/A
-
Description
Currently rename action is actually doing a copy and then a deleted.
This is slow and causes various issues. The idea would be to make the rename part of the store API and do "real" renames which for hibernate for example means directly modify the database to reflect the changed required to rename a document instead of loading the document, copy it and then delete the old one. Also all this would be done in a proper session which is a lot safer.
Attachments
Issue Links
- blocks
-
XWIKI-4287 XWikiDocument.rename changes object GUIDs
- Open
- causes
-
XWIKI-18610 Move a page with translations not working anymore
- Closed
- is related to
-
XWIKI-17341 Every documents loaded from the cache store should have the cache store as internal store
- Closed
- relates to
-
XWIKI-17903 Old entries are still displayed in Applications Panel after renaming an AWM application
- Closed
-
XWIKI-12184 Implement a real Document Rename to improve consistency and performances
- Closed