4

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.

2
  • I was expecting this to be a mis-post from SO main when I first saw this!
    – Flexo
    Commented Jan 17, 2012 at 13:28
  • 1
    deployed now ...
    – waffles
    Commented Jan 18, 2012 at 22:37

1 Answer 1

2

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.

1
  • I'll wait for this to go live before accepting it.
    – Mark Hurd
    Commented Jan 18, 2012 at 0:47

You must log in to answer this question.

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