Sometimes Can't Kill Running Query

[peterlaursen]

Please tell how you connect!

I briefly tried to reproduce this but I cannot.  

We will now try more systematically!

[peterlaursen]

This is reproduced (and partially explained) now.

The problem is that when you click a database in second connection a USE statement is sent.

If you swith back to first connection by clicking the title bar of the connection window (and doing nothing else before trying to kill the connection) no new USE statement is sent. The USE statement from second connection is still the active one.

But USE statements should be specific for each connection, I think.

And personally I am not sure why we need to address some specific database here at all!

We will study our own code again! 

[vygi]

well… it sounds really weired … because two different connections are mixed up:

this USE statement should be run on another connection and do not affect the first one.

Usually it is speciffic to connection but seems like it does not work like expected when a slow query is running. And everyithing is again OK when it's finished.

Anyway, I second that you should study your own code, as I can't explain what is going wrong here.

[peterlaursen]

Bikas is debugging his way through the code right now.

With all operations on data the program can have more USE statements 'in the air' simutaneoulsy and use the correct one.

What exactly happens with this STOP issue I cannot tell now, but probably can tomorrow.

This issue (and two very small cosmetical issues) are all what we are missing before 5.23 RC1 can be released. So it is priority now actually!

[peterlaursen]

Now fixed in the development tree.

RC1 with the fix is expected in 1-2 days.

[Author]

Posts