Change Details

Possible ideas so far: - Add virtual column that calculates full entity ids and then a secondary index on it, to top-level entity-terms linking tables. Problem with this is that those columns will appear in the tables => also in production. It might not matter though if they never get used by queries in production, but to keep such promise is hard once they are there. - Add secondary tables in labs that store mappings of full entity ids to top-level entity-terms linking tables //top-level entity-terms linking tables are tables such as `wbt_item_terms` and `wbt_property_terms` .. etc//

Possible ideas so far: - Add virtual column that calculates full entity ids and then a secondary index on it only in labs, to top-level entity-terms linking tables. Problem with this is that those columns will appear in the tables => also in production. It might not matter though if they never get used by queries in production, but to keep such promise is hard once they are there. - Add secondary tables in labs that store mappings of full entity ids to top-level entity-terms linking tables //top-level entity-terms linking tables are tables such as `wbt_item_terms` and `wbt_property_terms` .. etc//

Possible ideas so far: - Add virtual column that calculates full entity ids and then a secondary index on it only in labs, to top-level entity-terms linking tables. Problem with this is that those columns will appear in the tables => also in production. It might not matter though if they never get used by queries in production, but to keep such promise is hard once they are there. - Add secondary tables in labs that store mappings of full entity ids to top-level entity-terms linking tables //top-level entity-terms linking tables are tables such as `wbt_item_terms` and `wbt_property_terms` .. etc//