Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 157 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

Search appears to cache results for a short time. This is normally fine, since everyone sees the same results for the same query, but it causes oddness if the query includes user:me. For example, BoltClock searched for user:me [homework] on SO, and I searched for the same thing a moment later. I got his cached results (with all of his posts) instead of a list of my own posts. After a minute or so the query switched to giving me no results at all, and then finally to showing my own results. Is it possible for queries containing user:me (or anything else that might return different results for different users, like mod-only filters) to not cache? Or for search to convert it to user:UID first so the query won't match someone else's

share|improve this question
    
"Or for search to convert it to user:UID first so the query won't match someone else's" It is interesting to note that it already does this when displaying the search option in the sidebar. I imagine it'd be trivial to port this to the search field as well. – BoltClock's a Unicorn Jan 23 '12 at 18:07
    
@BoltClock'saUnicorn Yeah, and when I tried searching for user:309308 [homework] I still got your results, so I'm not sure how search is coming up with that – Michael Mrozek Jan 23 '12 at 18:10
up vote 11 down vote accepted

The key we were using for cache here was pre-replacement on the user:me to user:12345, in the next build this will be fixed. Also, it'll be fixed for the similar inquestion:this case.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .