Re: prepared statement query takes 3s for a few hundred lines - query issue

[Rick James]

> `longitude` double(16,14) NOT NULL,

Do not use (M,N) on FLOAT or DOUBLE. Furthermore, notice that you are implying that you can't go past +/-100 degrees of longitude.

> `country` varchar(3) COLLATE utf8_unicode_ci NOT NULL,
-->
`country` CHAR(3) CHARACTER SET ascii NOT NULL,

> `elevation` varchar(255)
I thought elevations were numeric? Also `bearing`.

EXPLAIN SELECT * FROM table;
is useless. Instead have the actual query after EXPLAIN.

Remove LEFT unless you need it. It is getting in the way of a particular optimization.

To `airspace_points` add
INDEX(airspace_id, grid)
INDEX(grid, airspace_id)