Some database indexes in TYPO3 tables are not optimal:
they include the sorting field in the wrong position.
MySQL will not use such index for sorting (sorting
field must always be in the end of index).
Change-Id: I9d900013ac5cabb7bdd7130ff2502674ee2c9b2a
Resolves: #21381
Reviewed-on: http://review.typo3.org/4317
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn
Reviewed-by: Mario Rimann
Reviewed-by: Xavier Perseguers
Tested-by: Xavier Perseguers
backend_layout_next_level int(10) DEFAULT '0' NOT NULL,
PRIMARY KEY (uid),
KEY t3ver_oid (t3ver_oid,t3ver_wsid),
- KEY parent (pid,sorting,deleted,hidden),
+ KEY parent (pid,deleted,hidden,sorting),
KEY alias (alias)
);
tx_impexp_origuid int(11) DEFAULT '0' NOT NULL,
PRIMARY KEY (uid),
KEY t3ver_oid (t3ver_oid,t3ver_wsid),
- KEY parent (pid,sorting,deleted,hidden)
+ KEY parent (pid,deleted,hidden,sorting)
);