Fix: Query results in public dashboard not loading when query ends wi…

[alexStrickner00]

What type of PR is this?

• [x] Bug Fix

Description

Dashboards accessed using the public url use the cached query result mechanism to fetch results after a query job is finished. When using parameterized queries, the frontend requests the data usually 2 times: one time after changing the parameter, and one time after the job is finished. The second request relies on the caching mechanism to find the cached result of the first request. The second request does not request auto_limit, which causes a lack of splitting and merging of sql statements. Because of that, the two sql queries differ in whitespacing and a trailing semicolon, which causes the query_hashes of both requests to differ.

That results in another job invocation and an empty query result in the second response in the frontend, which causes an endless loading spinner in the frontend and no fetched data.

By splitting the statements each time, you prevent these differences in the 2 sql queries.

How is this tested?

• [ ] Unit tests (pytest, jest)
• [ ] E2E Tests (Cypress)
• [x] Manually
• [ ] N/A

Splitting and merging statements should/can not break anything, otherwise the auto limiting would be buggy.