mirror of
https://github.com/plausible/analytics.git
synced 2024-12-23 09:33:19 +03:00
62fb285b71
* Increase max_parser_depth setting This is currently causing issues in production with exports w/ comparisons, but would blow up in other cases with sufficient data. The reason this is now blowing up is that we create a large AND/OR condition for breakdown comparisons. ecto-ch nests each conditional in its separate parentheses causing us to reach the default 1000 max_parser_depth limit We can improve this in a couple of ways: - Not add unneccessary parentheses in ecto-ch - Adding a new operator to make the AND/OR nesting require less conditionals, using arrays and tuples instead * Don't query comparisons for exports csv exports don't actually output any comparison data, so querying for it just causes issues. |
||
|---|---|---|
| .. | ||
| .env.dev | ||
| .env.test | ||
| ce_dev.exs | ||
| ce_test.exs | ||
| ce.exs | ||
| config.exs | ||
| dev.exs | ||
| prod.exs | ||
| runtime.exs | ||
| test.exs | ||