You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even when the number of views is higher than that it only returns 500 rows.
This makes the data that are shown on the /[websiteId}/?view=query incorrect and show different results (counts) when you apply a search.
Maybe it the LIMIT should be set to the number of views on the page.
Database
PostgreSQL
Relevant log output
No response
Which Umami version are you using? (if relevant)
v2.11.1
Which browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
Docker
The text was updated successfully, but these errors were encountered:
I don't think its the limit 500 that's causing the issues. the limit is applied after aggregating the data so its just limiting the result set to the top 500 groupings.
The query parameters would be the only metrics where applying a search changes the counts since in our db multiple query params are under a single column.
Describe the Bug
Even when the number of views is higher than that it only returns 500 rows.
This makes the data that are shown on the /[websiteId}/?view=query incorrect and show different results (counts) when you apply a search.
Maybe it the LIMIT should be set to the number of views on the page.
Database
PostgreSQL
Relevant log output
No response
Which Umami version are you using? (if relevant)
v2.11.1
Which browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
Docker
The text was updated successfully, but these errors were encountered: