We spoke lately about incorrect handling of Win-1251 data in MySQL 5.0 with SQLyog. I now think i have found another "bug" regarding that matter. So here it comes -

When i connect to my server (5.0 on unix) from a WinXP system i get my data ok and i was excited enough to delete my SQLyog 5.32 installation.

BUT. i have an "interactive_timeout" var set to 30 in my setup and when i leave SQLyog unattended for some time the same query i executed when i started SQLyog gave me .. only latin letters and no russian (win-1251) in the same mixed-language fields. My guess is that when reconnecting to the "gone away" server you are not using the same SET NAMES or some other code.

I hope to get reply soon as this annoys me greately. THANK YOU for otherwise great product.

PS. if you would make a checkbox "do not show this message today (for a week/month/whatever)" on the welcome screen of community edition (where you advertise enterprise edition) that'll be great. I know that i am satisfyed with free features and showing this message will never make me buying "enterprise edition", i'd rather donate some paypal for starting as fast as 5.23 Again, thatnk you!

"My guess is that when reconnecting to the "gone away" server you are not using the same SET NAMES or some other code." We will check this in detail. Nut we actually are (or should be) using the same function whenever reconnecting.

We have one example where the server 'forgot' the client and connection charsets setting after some time of inactivity. That one was a server issue!

What is the exact server and SQLyog versions that you are using?

MySQL 5.0.45-log x86_64
SQLyog 6.11 (it happened with 6.07 also)

and what was the server issue you mention? so i could check that, too.

Is the server a 64 bit Linux or Windows?


The old issue that I am referring to was simply that after some hours (typically a night) of inactivity the SET NAMES initially sent by SQLyog was sometimes 'forgotten' by the server and the datastream sent to the client (character_set_client) was encoded using the default and not the setting specified by SQLyog whne connected. As far as I remember this was an early 4.1 or 5.0 server build.


It is public holiday in India today, so only tomorrow we will be able to look into this.

it is
Linux praha-1 2.6.11.4-21.17-smp #1 SMP Fri Apr 6 08:42:34 UTC 2007 x86_64 x86_64 x86_64 GNU/Linux

congrats on your holiday waiting to hear back from you soon, thanx!

also..

on my second server, which is 4.0.27-standard-log on Linux 2.6.11.4-21.15-smp #1 SMP Tue Nov 28 13:39:58 UTC 2006 i686 i686 i386 GNU/Linux

i have interactive_timeout set to a value of 1000, but when i manually do a complex edit to any field in any DB with SQLyog 6.11, which takes some time, i get an error "mysql server has gone away" and all my edits are lost then. i have to reconnect (by pressing F5) and only then i can paste the data i used to enter before without reconnecting. This never happened with SQLyog 5.23 (i guess it just reconnect when sees mysql gone and reecutes query again).

There should be no difference between the versions in this respect!

Could you try to have both installed at teh same time and try both once you experience problems.
It may be a coincidence that something has happend with the connection about the same time that you upgraded.

I've tryed that and.. it worked fine.

that is:

/*[22:08:56][ 50 ms]*/ update `tags` set `id`='860',`ru_text`='Awards',`en_text`='',`bad`='1' where `id`='860'
/*[22:22:12][ 50 ms]*/ update `tags` set `id`='870',`ru_text`='LOST',`en_text`='',`bad`='1' where `id`='870'

and i made no single keypress in between two edits.

This setup is

version 4.0.27-standard-log
version_comment Official MySQL-standard binary
version_compile_os pc-linux-gnu
connect_timeout 240
delayed_insert_timeout 300
interactive_timeout 1000
wait_timeout 90

Also, do you have any news regarding my initial (a different one!) question as of Nov 1 2007, 12:57 AM?

I am sorry, but 'time flew' for us today. We will definitely pay attention to this tomorrow morning!

OK .. I'll summarize. You reported two issues

1) client charset gets lost after inactivity (this is a recent 64 bit Linux server)
We cannot reproduce. Can you on other servers? This may be a server bug!

2) 'server gone away' .. this may be a connection/firewall/OS issue and not a MySQL or SQLyog issue.


We cannot reproduce either of those issues. Not after 'playing around' with 'interactive timeout' either.


Please tell how you connect - direct, SSH, HTTP? I would not be surprised if the 2nd issue is SSH-related!

My summary will be LOT shorter - NONE of these two happen with YOUR SQLyog 5.23. both times i use direct connection.

i again have to stick with 5.23 for a little while and search for a better devs, who can find differences in their two products "to reproduce" i am really-really upset, after i told so many friends to use your Yog, you throw me away without asking for more details, test accounts, etc. you just don't give a shit and that dissapoints.

We have tried very hard to reproduce all issues with no success.

"you throw me away without asking for more details, test accounts"
... Whatever information you can give, give!! And create a support ticket if you want privacy!