Bug When Stopping A Slow Running Query

[peterlaursen]

And it is SQLyog 5.2 RC2 ?

[scottah]

peterlaursen wrote on Nov 17 2006, 06:26 AM:

And it is SQLyog 5.2 RC2 ?

umm help about says 5.2 Beta 11

[peterlaursen]

Reproduced here now too.

We are (re)searching ….

[peterlaursen]

Fixed in the development tree.

Issue was that is the query did not use `database`.`table` notation but only `table` notation, the latest USE statement got lost if SQLyog reconnected – what it frequently does with so-called 'slow servers'.

Now it will USE the database shown in the combo-box in such situation.

[scottah]

peterlaursen wrote on Nov 17 2006, 12:01 PM:

Fixed in the development tree.

Issue was that is the query did not use `database`.`table` notation but only `table` notation, the latest USE statement got lost if SQLyog reconnected – what it frequently does with so-called 'slow servers'.

Now it will USE the database shown in the combo-box in such situation.

Hmm I wonder what has changed… I have only noticed this new behaviour lately (ie the last 1 or 2 releases..) perhaps my server has turned into a so-called 'slow server'

[peterlaursen]

I shall not tell what happened. it need not be the MySQL server. Could be a trivial harware issue (cable, router, switch , transmitter) as well.

If you are in control of the server you can enable the 'general log' by inserting something like

log = mylog.log

in the [mysqld] section of the my.ini/my.cnf file and you can see how often it reconnects.

[Author]

Posts