-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Case insensitive parameters in Redash query result cache #2137
Comments
The problem is in the I think we can stop lower casing the query in this method. We don't need to dedup that aggressively. |
Hi, I've looked around at the code, reproduced the error and I think this can be my first PR. |
@ClaudioDavi yes, but also need a migration to recalculate the query hash for all existing queries. |
Ok, thanks @arikfr ! Do you have any migration examples for me to have a look and follow through? |
Generating the query hash from the query text with no lowercasing of the query text allows case-sensitive parameter values in the dashboard to have different cache entries. Fixes getredash#2137
Generating the query hash from the query text with no lowercasing of the query text allows case-sensitive parameter values in the dashboard to have different cache entries. Fixes #2137
Generating the query hash from the query text with no lowercasing of the query text allows case-sensitive parameter values in the dashboard to have different cache entries. Fixes getredash#2137
Issue Summary
Redash may display wrong results for query with case sensitive parameter. It looks like results cache is ignoring param letters size.
Steps to Reproduce
In the last step you should receive visualization for parameter 'test' even when parameter value is set to 'TEST'
I have been able to reproduce this scenario on demo.redash.io. To reproduce do:
You should see rows from dashboard table with name
test
You should see rows from dashboard table with name
test
even when parameterdashboard_name
is set toTest
. After refreshing visualization result changed to proper one.Technical details:
The text was updated successfully, but these errors were encountered: