This is needed if we want to switch the SqlEntitiesWithoutTermFinder implementation to not make use of the wb_entity_per_page table. Changing the implementation to join against the page table by using a str replace on the entity id is less efficient, so we need to be sure we can restrict that in production to properties (where we only have a few thousand rows).
Description
Description
Event Timeline
Comment Actions
How big is the difference between the two SQL queries? Can't we optimize it more? Is the difference really that relevant for two special pages that nobody uses anyway?
Comment Actions
Significant. The old query used an indexed integer column for joining, while the new uses a REPLACE() on a column for joining.
I can't see how we can optimize it more with the current wb_terms table structure.
Probably not, that's why we remove the support for Items. The new query might be so bad that it could be used in a harmful way if you have the possibility to trigger scanning multiple million rows.