[kasi]

I am using SQLYog Enterprise 5.20

peterlaursen wrote on Feb 14 2007, 06:28 AM:

Instead of you guessing the reason for this you could give us a test case so that we can solve it! 😉

I didn't guess the reason. I changed the the tunneler script, so that it dumps me all queries, that are send to the server, to a log-file. I alse dumped the connection state using “show variables like 'character_set_%'” before each mysql_query. So I know that the data from the database is in latin1 and I guessed that the server locally sends “set names utf8” because all special characters are gone.

Also when I do “mysql_query('set names utf8') just after mysql_connect() everything works correct (except sending own queries).

This only happens when doing “Copy selected database to an other HOST/DB”.

Export as Batch-script and Database Synchonisation Wizard are working correct (doing set names utf8 and fetching utf8 data).

KASI

[kasi]

The Problem is fixed now.

It wasn't the Apache Server but PHP. There was a “auto_prepend_file” defined in php.ini which had a closing ?> tag with a new line after that.

KASI

[kasi]

Now I found the problem.

For reasons I don't know the webserver sends a newlinw char before each content: So you can reproduce my error, when you insert a “echo chr(10);” at the beginning of the Tunnel-script.

It looks like that the connection that asks for the tunnel-version, doing a

“POST /SQLyogTunnel.php?app=sqlyog&version=5.2 HTTP/1.0” and receiving a

“TunnelVersion:5.2” response, can not handle that!

I hope you can add some content trimming so that I can connect to that server using version 5.2.

thanks

KASI

[kasi]

I guess I found the problem.

Version 5.2 uses multiple connections to the webserver simulatinously and that is not allowed there.

I again checked version 5.13 and it uses only 1 connection. So something must have been changed between this version.

Question now is why does SQLyog do that and how can I change that??

thankes

kasi

[kasi]

peterlaursen wrote on Nov 24 2006, 06:36 AM:

Please answer:

1) Your are perfectly sure that this problem occured the very same moment as you upgrade?

2) What was the version that you used before?

Yes I am shure. I had the same problem with that server when upgrading to version 5.17, so I switched back to version 5.13

Just reinstalled version 5.13 and it works.

version 5.13 works fine

version 5.17 no Test Connection and no Connection

version 5.2 Test Connection ok Connection fails

it is not the connection:keep-alive thing, this has been changed

any ideas ??

thanks

KASI

[Author]

Posts