479792 - Normalize all date values to the same type before making queries from hours/days/weeks

Status: RESOLVED WONTFIX

(Socorro :: General, task)

Description

[Austin King [:ozten]]

From #breakpad
ss: What's the difference between these two queries:
[08:58am] ss: http://crash-stats.mozilla.com/?do_query=1&product=Thunderbird&branch=1.9.1&version=Thunderbird%3A3.0b2&query_search=signature&query_type=contains&query=&date=&range_value=1&range_unit=weeks
[08:58am] ss: http://crash-stats.mozilla.com/?do_query=1&product=Thunderbird&branch=1.9.1&version=Thunderbird%3A3.0b2&query_search=signature&query_type=contains&query=&date=&range_value=7&range_unit=days
[08:58am] ss: I'd think 1 week == 7 days
[08:58am] ss: But 'days' queries tend to be faster than 'week' queries.
[09:00am] aking: CAST(1 weeks' AS INTERVAL) versus CAST(7 days' AS INTERVAL)
[09:00am] aking: nothing else about the query changes

1) We should validate which of hours, days, or weeks is that fastest in Postgres engine. 
2) We should normalize the query params to this type

Additional benefits are data caching of queries will have less permutations.

Comment 1

[Michael Morgan [:morgamic]]

These are the same speed after the last refactor.