[TYPO3-core] Moving of elements (records) and pages in workspace
9f4eetb02 at sneakemail.com
Wed May 9 15:53:02 CEST 2007
Kasper Skårhøj wrote:
> When I worked in Paris in March I tried to optimize their site. I found
> that SQL statements in the backend selecting records in a workspace are
> scanning the whole table! The reason is that they look up records like
> this: "where (t3ver_oid=X OR uid=X)" Because it is an OR operation the
> index table is NOT used at all and it cannot be used according to MySQLs
> own explanation of how indexes work. It should say that both t3ver_oid
> and uid is in the same index together. But even thought you could
> imagine this to work, MySQL doesn't use it - hence it scans the whole
> table in the Web>List module! I don't know yet how to solve this issue.
> It is only found in the backend I believe.
I remember that MySQL may decide not to use index if it believes that it
can do it faster with full table scan. May be this is your case?
"It is our choices, that show what we truly are,
far more than our abilities." (A.P.W.B.D.)
More information about the TYPO3-team-core