Nick Fanion

Not quite the same thing, but seems related to https://github.com/evidence-dev/evidence/issues/1479 I think unselected inputs should return a predictable value (be that `null` or something else) and not cause queries to...

Would changing the behavior of `selectAllByDefault` or allowing a `selectNoneByDefault` that returns null or a value that lets us write SQL to skip the where clause when nothing is selected...

Seems to be the reverse issue of #2081 but I understand why handling of zeros/nulls was changed.

Have you tried dollar quoting? You wrap the filter input in double-dollar symbols ($$). I use it for my filter values with apostrophes and other special characters. I find it...

I asked the original question on Slack. Percent change aggregations need `totalAgg=weightedMean` _and_ `weightCol` set to the "old value" (for example, if comparing `sales` to `sales_year_ago`, `weightCol` should be `sales_year_ago`)....