[peterlaursen]

.. and also if you did not alerady, please try to  reboot your system. Windows memory corruption unrelated to SQLyog can cause this. Or another running application can.

[peterlaursen]

You may also send a mail to [email protected] with the file attachment.

 

The SQLyog editor is based on the Scintilla library (http://www.scintilla.org/). I wonder if you have some other program runnng changing the behavior of  Scintilla.  Could you please try with no other program running – and preferably after a fresh reboot. 

[peterlaursen]

The file was not attached. You need to do in 2 steps: 1) upload 2) attach to post (the interface can be a little triggy to understand first time).

 

I have tried to reproduce this!

[peterlaursen]

I cannot reproduce with SQLyog 11.52.  But some  formatting details that were lost in HTML may matter.  So still please attach a file with the script.

[peterlaursen]

Pleae attach the SQL script as a file attachment (and please zip it).  Once it gets HTML-formatted as here, it is not he same.

 

Also please tell your SQLyog version. We have fixed such issues before so old versions may have this problem in some  cases.

[peterlaursen]

Would you mind try with 11.51? We have tested in various Linux environments (but probably not exactly like yours).

[peterlaursen]

This FAQ documents:

http://faq.webyog.com/content/15/47/en/is-there-any-difference-between-sja-for-linux-and-sja-for-windows.html

[peterlaursen]

Please try to use the option to define a ‘keep-alive’ interval for the connecton.  Please see atached image.

 

[attachment=1959:alve.jpg]

 

 

 

This is a network issue that we (or anybody else) have not really been able to explain.  A new connection is fast but a reconnect is extremely slow. I believe that you would exerience the same with any client using persistent connection (PHP and ODCB don’t for instance) runnng from same machine

 

We have a (very) old blog about this:

http://blog.webyog.com/2009/09/02/%E2%80%9Cmysql-server-has-gone-away%E2%80%9D-part-2-session-timeout/

(when this blog was written the ‘Session Idle Timeout’ setting had just been added, but the ‘keep-alive’ interval setting is newer).

 

Also SQLyog documentation explains this.  Here is a link to and a quote from the online version (but same is available from  help .. help -menu): 

https://static.webyog.com/docs/SQLyog/Direct_Connection_SQLyog_MySQL_Front_End.htm

 

Session Idle Timeout: The option to define timeout for the session (different from the global setting) is possible with MySQL servers from 5.0 and up.  However, most users will need not to care about it – not even if server timeout setting is low. SQLyog will reconnect if connection was lost since last query was run. Most often user does not even notice. However, we have reports of situations where the network takes very long time to process such reconnect request. In this situation setting the timeout from the client will prevent the situation. Also SSH-users connecting to SSH servers/daemons that are slow to establish connection and where MySQL has a low timeout setting can use this option with advantage.

Keep-Alive Interval: In some cases, setting a high session idle timeout does not prevent disconnection. This option sets a time interval at which mysql_ping() will be executed. This should only be used if setting a high session timeout does not prevent disconnection. Also the interval specified should be the highest possible interval which still prevents disconnection.

 

[peterlaursen]

Why do you think then it is a problem with SQLog and not Hostgator? I suggest you contact Hostgator support about tis.

[peterlaursen]

I think this FAQ explains:

http://faq.webyog.com/content/17/187/en/problems-creating-a-functional-dsn-on-64-bit-windows.html

[peterlaursen]

As far as SQLyog is concerned it does not matter.  SQLog always uses UTF8 internally no matter how data are stored on the server. Please refer: 

http://faq.webyog.com/content/8/148/en/do-i-need-to-set-names-to-display-characters-of-my-language.html.

 

Besides this is not  the best place for asking web application design questions. You are welcome to do so, but it is unlikely that you will meet experts in that matter here. However we at Webyog have been using UTF8 for all our web for more than 5 years now (and that is unrelated to HTML5) .

[peterlaursen]

I do not understand!

 

Could you elaborate, please? You may attach screenshots etc. here if it helps.

[peterlaursen]

The option to base64-encode was introduced in SQLyog as a workaround for a bug in a PHP XML-library, where some special characters were not always encoded cotrectly. Probably your webhost has installed an affected PHP-veron/XML-library. When using base64 everything transferred is ASCII. But it results in a 50% overhead in the data stream, as every 2 characters are encoded as a 3-byte sequence.

 

You may also bumped into this bug (that is ours): https://code.google.com/p/sqlyog/issues/detail?id=77

[peterlaursen]

“could include a few lines about the use made of these comments in the sql that is generated”.

 

What we do here is the de-facto standard of what any MySQL tool dumping or copying SQL database objects do  – including the official ‘mysqldump’ tool.  It is simply something every MySQL user should know.  MySQL has lots of ‘oddities’ compared to other RDBMS and as provider of a client it is not our job to rewrite the MySQL manual.

[peterlaursen]

Well .. this is now an old post.   Have you  solved this now, or do you still need help?

[Author]

Posts