Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.VincentMassol
	1	+XWiki.enygma

Content

...	...	@@ -94,6 +94,7 @@
94	94	create index ase_param3 on activitystream_events (ase_param3(200));
95	95	create index ase_param4 on activitystream_events (ase_param4(200));
96	96	create index ase_param5 on activitystream_events (ase_param5(200));
	97	+create index solr_iterate_all_documents on xwikidoc (XWD_WEB, XWD_NAME, XWD_LANGUAGE, XWD_VERSION);
97	97	// Only required if you use stats (feature is off by default)
98	98	create index xws_number on xwikistatsdoc (XWS_NUMBER);
99	99	create index xws_classname on xwikistatsdoc (XWS_CLASSNAME);
...	...	@@ -109,7 +109,7 @@
109	109	{{info}}
110	110	Note to XWiki developers: The following indexes could be created automatically though since they're less than 255 characters and thus should be added in a future version of XWiki so that they don't need to be created manually:
111	111
112		-{{code language='mysql'}}
	113	+{{code language="mysql"}}
113	113	create index xws_number on xwikistatsdoc (XWS_NUMBER);
114	114	create index xws_classname on xwikistatsdoc (XWS_CLASSNAME);
115	115	create index xwr_number on xwikistatsreferer (XWR_NUMBER);
...	...	@@ -319,7 +319,7 @@
319	319	In current row format, BLOB prefix of 768 bytes is stored inline.
320	320	{{/code}}
321	321
322		-When you are using a MySQL Server 5.6.20 you can get a "row size too large error."
	323	+When you are using a MySQL Server 5.6.20 you can get a "row size too large error."
323	323	In the release notes, it is explained that a innodb_log_file_size which is too small will trigger a "Row size too large error."
324	324
325	325	You can solve the problem by changing the innodb_log_file_size in the my.ini text file.