<
From version < 67.1 >
edited by Thomas Mortagne
on 2015/09/25
To version < 69.1 >
edited by Thomas Mortagne
on 2015/09/25
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -201,7 +201,7 @@
201 201  
202 202  The heart of the implementation is that the field that used to contain the unique document space now contain the possibly Nested Space Reference. In practice it means that:
203 203  
204 -* "##.##" (dot), "##:##" (colon) and "##\##" (baskslash) characters, which are part of a Space name will now be escaped (using the "##\##" character) in the ##space## (##XWD_WEB##) field from the Document's table in the Database. For example a space named ##Space:with.special\char## will be stored as ##{{{Space\:with\.special\\char}}}##.
204 +* "##.##" (dot), "##:##" (colon) and "##\##" (baskslash) characters, which are part of a Space name will now be escaped (using the "##\##" character) in the ##space## (##XWD_WEB##) field from the Document's table in the Database. For example a space named ##Space:with.special\char## will be stored as ##Space\:with\.special~\~\char##.
205 205  * Same as for the database, the ##XWikiDocument/Document#getSpace()## methods now return a serialized Reference to the Space instead of what used to be the unique Space name (basically it return what's in the database). Same logic for ##XWikiDocument#setSpace()##. Those field have been deprecated a long time ago but they are still used in lots of places...
206 206  * Various APIs are also affected by this Space name to Space Reference input change:
207 207  ** ##XWiki#getSpaceDocsName## methods (both in the public and private XWiki API)
... ... @@ -641,7 +641,7 @@
641 641  
642 642  = Performances tests compared to 6.4.5 =
643 643  
644 -There hasn't really been much performance work on this version (it will most probably start again in 7.3 and 7.4) which was dedicated to nested spaces support so we get mostly the same results than in [[7.1>>test:Performances.Jetty HSQLDB single wiki 712 to 72]]. The important point here was to check if nested spaces had much impact on performances.
644 +There hasn't really been much performance work on this version (it will most probably start again in 7.3 and 7.4) which was dedicated to nested spaces support so we get mostly the same results than in [[7.1>>test:Performances.Jetty HSQLDB single wiki 712 to 72]]. The important point here was to check if nested spaces refactoring had much impact on performances.
645 645  
646 646  {{warning}}
647 647  It's important to note that the way to measure performances has changed in this version (used to me a range of 10 values taken one by one and we are now using [[Dumbbench>>https://github.com/tsee/dumbbench]] usually on 100 values) and this is why you'll see some differences if you compare this Performance report with the one in [[7.1 release note>>ReleaseNotesXWiki71]] for example.

Get Connected