Chris Hill-Scott f96c43f5bc Store GeoJSON in a separate table ...

I think that even with good indexes, querying the area names from one
table is always going to be slow because there’s so much GeoJSON to scan
past.

This commit splits the data into two tables, one for the names and
grouping IDs and one for the blobs of GeoJSON. So for most pages the app
will never even be looking at the table where the GeoJSON is held.

I don’t know if this is a proper, normalised way of structuring the
data, but it does go brrr.

2020-08-12 10:43:01 +01:00

79 MiB

Raw History

The file is too large to be shown. View Raw