Developer comments
This comes directly as a result of the changes in [12975, this issue].
Might be related in changes of charset and collation.
This is unrelated to the charset and table schema changes. When running a store in two languages, english and german, it affects only english. The english query takes 1.9 seconds, the same statement using the german labels takes 0.3s. Very strange and hard to trace down.
The query optimizer makes the choses the wrong execution plan. Not sure why he messes up, but messing up he does. In his defense: it seems that he gets fed wrong stats.
This affects large systems only (high topic count, high domain topic type count). Best strategy seems to the straight join. There is only two options select type first or full table scan the search term. The full table scan is constant but might slow search down for single type searches when there is only a few instances.
|
Work sessions2
| Start |
2024-12-04T07:57:54
|
| End |
2024-12-04T11:34:36
|
| Participant |
Robert Cerny
|
| Start |
2024-12-05T07:40:34
|
| End |
2024-12-05T19:59:44
|
| Participant |
Robert Cerny
|
|