[peterlaursen]

1) It looks very much like this issue that I reported.

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

It is not SSH related.

Please execute

SHOW VARIABLES LIKE '%character%'

on both the remote and the local 5.0 server

Can you paste the complete HISTORY in here.  It will tell us what succeds and what does not!

2) the 'gone away' thing.  We have a few more similar reports. We are working on it.

[peterlaursen]

unoubtedly compression is useful with big exports and imports to/from remote servers (as your own example shows).  For the common use of the GUI functionality I do not think it make any notable difference.

We will discuss this next week.

[peterlaursen]

I am moving the post to the SQLyog category (you posted in MONyog category!)

[peterlaursen]

OK .. I was just informed by a test engineer in B'lore that the crash can be reprocued when connected to MySQL 4.0 or 3.x – not higher versions. Can you confirm the MySQL version to be 4.0 or lower in your case?

[peterlaursen]

Not reproducable here either on a Danish Vista (and an empty table).

I think we will need to find out if it is data related. Can you reproduce a crash too with an empty table?

[peterlaursen]

flickering issue confirmed.

the SELECT statement makes the data area flicker, and on my system CPU goes abot 50 % even when there is no activity!

[peterlaursen]

reproduced as you describe with 5.29 as well as 6.0 beta 4. Actually we fixed in 6.0 beta2 for the common gui (DATA tab etc) but seems to have forgotten that 'copy .. to other' is another code module!

Thanks for reporting!

[peterlaursen]

and ..

PROGRAM VERSION PLEASE!

always program version .. always program version .. program version .. program version .. version .. version 😕

[peterlaursen]

It is a known issue.  Please refer to:

http://code.google.com/p/sqlyog/issues/det…mp;can=2&q=

I think every SQLyog version is affected.

Byt PLEASE ALWAYS TELL in every new discussion you start, what program version you use!

I also asked for that in your other thread, but you did not!

Let us discuss when we can 'push in' a solution to this.

[peterlaursen]

I am moving your post to the SQLyog category!

[peterlaursen]

We will try to follow your description.

BTW: you do not mind if I move this post to the SQLyog category? 😛

[peterlaursen]

Did you try to 'connect using the same details' from the 'file' menu  (or just CTRL+N) ?

that should connect createing a new window and it should not be necessary to close the existing one!

Quote:

My Queries and my history is gone!

yes, of course if you close the window!  You will have to save the queries (to a file or a favorite).  History can be copied to clipboard and saved to a file.

You claim that SQLyog does not TRY to reconnect.  How can you tell?  Maybe it tries but it cannot?

I will discuss with developers and get a detailed undestanding of how reconnection works, when it works and when it does not and what you can or cannot expect!  I will reply here and/or write a FAQ on this!

[peterlaursen]

I am afraid I do not fully understand this:

Quote:

I think it reconnects to this different server but does not reconnect to the current one.

You experience that reconnects fails with this specific server, but normally it works?

Did you experience this once or is it reproducable?

Do you know if the server may have been unreachable for a period of time that night?

[peterlaursen]

When you are using the term 'canvas' do you mean that you are using the Query Builder?

From the screenshots I understand that it is not the case, but please confirm!

Undoubtly some memory corruption. Not sure that this is a SQLyo issues. But likely it is. We will have to look detailed into it.

Unless you can say that some other program started when problems appeared.

Can you explain what you are doing? In case you experience this again the HISTORY recordings would be valuable?

SQLyog version, please? First time you try this version? Or is it the same old version as you always used?

[peterlaursen]

ok .. I call in a 'techie'

Just note that this is not an autehtication but a connection issue.  It is not the MySQL server that won't let you connect – it is some other server, router, proxy or whatever networking HW and SW is there!

[Author]

Posts