I've upgraded mysql on windows server to 8.0.21 version.
I have a query that runs 7s using the connector / navicat client both on localhost and remotely.
Same query runs 0.9 on Workbench.
Query returns 1 row.
explain:
Select type: Simple
Type: ALL
Possible keys: cola-colb
key: null
key_lenn: null
rows: 10M
filtered: 16.66
Extra:
using WHERE.
Something is wrong in the connector to this server's version.
table has 10M records and it's on INNODB:
CREATE TABLE `e` (
`cola` decimal(39,0) unsigned DEFAULT NULL,
`colb` decimal(39,0) unsigned DEFAULT NULL,
`a` char(2) COLLATE utf8_bin DEFAULT NULL,
`b` varchar(64) COLLATE utf8_bin DEFAULT NULL,
`c` varchar(128) COLLATE utf8_bin DEFAULT NULL,
`d` varchar(128) COLLATE utf8_bin DEFAULT NULL,
KEY `idx_ip_cola_colb` (`cola`,`colb`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin
and query is:
SELECT a, b, c FROM e WHERE cola <= 281471982716236 and 281471982716236 <= colb;
I have a query that runs 7s using the connector / navicat client both on localhost and remotely.
Same query runs 0.9 on Workbench.
Query returns 1 row.
explain:
Select type: Simple
Type: ALL
Possible keys: cola-colb
key: null
key_lenn: null
rows: 10M
filtered: 16.66
Extra:
using WHERE.
Something is wrong in the connector to this server's version.
table has 10M records and it's on INNODB:
CREATE TABLE `e` (
`cola` decimal(39,0) unsigned DEFAULT NULL,
`colb` decimal(39,0) unsigned DEFAULT NULL,
`a` char(2) COLLATE utf8_bin DEFAULT NULL,
`b` varchar(64) COLLATE utf8_bin DEFAULT NULL,
`c` varchar(128) COLLATE utf8_bin DEFAULT NULL,
`d` varchar(128) COLLATE utf8_bin DEFAULT NULL,
KEY `idx_ip_cola_colb` (`cola`,`colb`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin
and query is:
SELECT a, b, c FROM e WHERE cola <= 281471982716236 and 281471982716236 <= colb;