[Ritesh]

Oops. Seems that the file did not get updated.

Please download it again as specified at http://www.webyog.com/forums/index.php?act…st=0&#entry5999

[Ritesh]

There are many reasons for the above error. Check out http://www.google.com/search?complete=1&hl…way&btnG=Search for more details.

[Ritesh]

sergius wrote on Jun 21 2005, 07:41 PM:

Minor bug in for SQLyog 4.05 (I glanced through the bugfix lists for versions 4.06 and .07 and didn't see this one); OS = Windows 2000.

When you execute a statement in SQLyog, the status line reports the (probably)  correct execution time; for a multiple-statement script, it's the time for the last statement.

However, the message tab seems always to report “0 ms taken.”

This is not a bug.

The MESSAGE tab will show time taken to execute the query. The STATUS bar will show the time taken to fetch the data from the server to the client.

90% of the time MESSAGE tab will show 0ms taken as it does not take much time for MySQL to parse and execute the query.

[Ritesh]

peterlaursen wrote on Jun 22 2005, 03:09 AM:

It's on localhost. Direct API-connect.

Try it yourself with one of the tables form my webserver (dump it to your local).

I just tried on 40000 rows and it seems to be OK. It takes time to get 40000 rows (which is expected) but it shows the data.

[Ritesh]

Bug fixed.

Fix will be available from BETA 2.

[Ritesh]

Looks like they are considering it as “Not A Bug”.

[Ritesh]

Bug details can be found at:

http://bugs.mysql.com/bug.php?id=11496

[Ritesh]

Cant seem to find a issue like this in the MySQL Bug System. :huh: I am opening a new bug at http://bugs.mysql.com

[Ritesh]

The SJA problem you reported earlier is similar to this.

[Ritesh]

I have been working on your issue for the last 2 hours and even I reached the same result. I think its a problem with MySQL. It does not seem to handle '\' correctly in PKs.

[Ritesh]

Very strange as I am not able to reproduce the error. The data-tab works perfectly for me.

Do you see any corresponding INSERT/UPDATE/DELETE statement in the History Tab. I checked the option with and without tunneling. Everything seems to be working.

[Ritesh]

Is it possible to reduce the set of data to reproduce the error more easily?

[Ritesh]

You had reported an error regarding incorrect colorisation of SQL statements in editor. Can you mail me a dump of your database and the query to reproduce the error?

[Ritesh]

Are you connecting to a remote machine with tunneling on or it is a direct connection to your local server?

Quote:

It must be the heat in India …

It has started raining where we are located so the weather is pretty much OK 😀

[Ritesh]

I still have the connection details of your server. I will look into the matter as soon as possible.

[Author]

Posts