>> A use case that I see quite a lot of is needing to do reports and other >> calculations on data per day/hour/etc but in the user's time zone. The >> way to do that is fairly trivial, but it's not obvious what it does so >> reading queries becomes just a little bit more difficult.
+1 A client encountered this exact problem last week, and I was surprised that the parameter didn't already exist.