Bug: range parameters in wrong order

[sebastian]

Look at this query:

                select
                    min("Longitude")
                from "london_street"
                where "Longitude" between 0 and -0.5668908806130065

We expect the where clause to read:

                where "Longitude" between -0.5668908806130065 and 0

[dandanlen]

I think this is related to #91

In fact we want something more like this to shift the range lower than the previous estimate:

where "Longitude" between (-0.5668908806130065 * 2) and -0.5668908806130065

But either way the params are back-to-front.

[sentry-io[bot]]

Sentry issue: EXPLORER-F