How can I optimize sql for price and timestamp fields? - mysql

Question

checking explain (mysqlnd 8.1):
explain analyze SELECT *
FROM `ts_products` WHERE `ts_products`.`creator_id` = '2' AND
`ts_products`.`title` like '%no%' AND
`ts_products`.`status` = 'A' AND
ts_products.published_at >= '2022-04-01' AND
ts_products.published_at < '2022-04-21' AND
ts_products.sale_price > '261'
ORDER BY `sale_price` asc
on table :
CREATE TABLE `ts_products` (
`id` bigint unsigned NOT NULL AUTO_INCREMENT,
`creator_id` bigint unsigned NOT NULL,
`title` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
`status` enum('D','P','A','I') COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'D' COMMENT ' D => Draft, P=>Pending Review, A=>Active, I=>Inactive',
`slug` varchar(260) COLLATE utf8mb4_unicode_ci NOT NULL,
`sku` varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL,
`regular_price` decimal(9,2) DEFAULT NULL,
`sale_price` decimal(9,2) DEFAULT NULL,
`in_stock` tinyint(1) NOT NULL DEFAULT '0',
`stock_qty` mediumint unsigned NOT NULL DEFAULT '0',
`has_discount_price` tinyint(1) NOT NULL DEFAULT '0',
`is_featured` tinyint(1) NOT NULL DEFAULT '0',
`short_description` mediumtext COLLATE utf8mb4_unicode_ci,
`description` longtext COLLATE utf8mb4_unicode_ci,
`published_at` datetime DEFAULT NULL,
`created_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
`updated_at` timestamp NULL DEFAULT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `ts_products_slug_index` (`slug`),
UNIQUE KEY `ts_products_sku_index` (`sku`),
UNIQUE KEY `ts_products_creator_id_3fields_index` (`creator_id`,`sale_price`,`status`,`title`,`published_at`),
KEY `ts_products_status_title_regular_price_published_at_index` (`status`,`title`,`regular_price`,`published_at`),
KEY `ts_products_status_5fields_index` (`status`,`in_stock`,`has_discount_price`,`is_featured`,`title`,`published_at`,`stock_qty`,`sale_price`),
CONSTRAINT `ts_products_creator_id_foreign` FOREIGN KEY (`creator_id`) REFERENCES `users` (`id`) ON DELETE RESTRICT ON UPDATE RESTRICT
) ENGINE=InnoDB AUTO_INCREMENT=801 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
I see that ts_products_creator_id_3fields_index index is selected and seems good, but looking at output :
-> Index range scan on ts_products using ts_products_creator_id_3fields_index over (creator_id = 2 AND 261.00 < sale_price), with index condition: ((ts_products.creator_id = 2) and (ts_products.title like '%no%') and (ts_products.`status` = 'A') and (ts_products.published_at >= TIMESTAMP'2022-04-01 00:00:00') and (ts_products.published_at < TIMESTAMP'2022-04-21 00:00:00') and (ts_products.sale_price > 261.00)) (cost=20.06 rows=44) (actual time=0.070..0.179 rows=2 loops=1)
I wonder if how signs ">=" / "<" / ">" work where. AS far as I know only '=' works for indices.
If there is sense to add sale_price and published_at in ts_products_creator_id_3fields_index index ?
How can I optimize this request ?
Thanks!

Answer 1

This might help:
INDEX(creator_id, status, sale_price)
There is one column that is unindexable (title like '%no%') because of the leading wildcard, and 2 ranges: published_at and sale_price. I picked the latter because it might be useful both in WHERE and in ORDER BY.
Please provide the EXPLAIN.
As discussed in Index Cookbook , columns tested by = should come first in a composite index, followed by one 'range' column.