Open simonw opened 4 years ago
OK, I fixed that bug... but there's a much worse one. The SQL queries generated in the JavaScript don't take the current page filters into account, so the numbers they display apply to the main table, not to the filtered version.
Fixing this is going to be a lot harder. It may require a complete overhaul of how the plugin works under the hood.
Or... I bet I can fix it by exposing the SQL query used on the page (using a template variable) and then rewriting the SQL queries to use subselects.
That could even eventually mean this plugin can work on the arbitrary database query SQL results page!