Meta Stack Exchange is a question and answer site for meta-discussion of the Stack Exchange family of Q&A websites. It only takes a minute to sign up.
Sign up to join this community
I first saw this with my edited #Temporary tables and indexes work and now see it with my simple SELECT 1 then 2 Test.
The first query, whether it is cached or a new one (by ensuring you go to a database that hasn't run the query yet), works fine.
But if you then click Run Query again it is using another query. In the first case I think it is the original query before revisions were set up, and in the second one it is someone else's random query.
When the response is returned, the URL that the form submits to sometimes needs to be updated. This was not one of those times, but it happened anyway, and the revision ID was replaced with the query set ID.
By making sure the action needs a query set ID added before appending it, this problem seems to go away.
