[Ritesh]

This is a nice idea.

In the meantime, you can use my_strtok() function available in SQLyogTunnel.php for tokenising the queries.

[Ritesh]

Not a bad idea.

But with ALTRE SP and all, we need to put the delimiter as $$ and not ;. Basically, we need to add the query in the history box with the delimiter.

[Ritesh]

Couple of bug fixes regarding charsets. This area is still under development and expect some more fine tuning in coming BETAs.

[Ritesh]

Yes, indeed. This version fixes this issue.

I imported your data without any problem. This process was earlier giving errors.

[Ritesh]

This is strange though. If there is any server/configuration problem then you should not receive TUNNEL version mismatch error.

BTW, I will suggest that you try out v5.1 BETA 4. It was couple of improvements regarding HTTP Tunneling.

[Ritesh]

This is correct.

Since we changed the HTTP post/receive method, it results in HTTP error.

v5.11 is due to the fact that we were using 5.1 in the earlier BETAs and there was a major change with BETA 4. Thus the tunnel version is 5.11.

[Ritesh]

Very strange.

Isnt your SQLyogTunnel.php showing:

/* version constant */

$tunnelversion = '5.11';

[Ritesh]

Cirunz wrote on Mar 20 2006, 01:31 PM:

Hi to all

I'm experiencing the some problem, my version is 5.02 free edition that I've just downloaded. The SQLyogTunnel.php file report version 5.0 but I've got it from the install dir and it is the first time I install SQLYog.

That is correct. 5.02 uses the original v5.0 TUNNELER file. There has been no change regarding HTTP Tunneling code from 5.0.

Are you sure you are using v5.02 and v5.1 BETA?

[Ritesh]

Sorry for not posting for BETA 3.

The files are getting uploaded as I write this. BETA 4 news in another 2-3 hours.

[Ritesh]

We just commited the final patch for 5.1 BETA 4. This issue will be fixed in BETA 5.

[Ritesh]

nicmar wrote on Mar 18 2006, 08:45 AM:

I'll mail you a dump of the entire db, ritesh.

It's not confidential, but don't post anything on the forums thanks, there are some personal details, but mostly test data.

Btw, i'm using PHP 4.4.1 and Mysql 4.0.26 both on my localhost and my ISP .

I've sent the file to ritesh via mail.

Thanks, I have received the dump. I will work on it now. Dont worry, no details will be published anywhere.

[Ritesh]

Thanks for your observation. I have added it in our TO-DO list. We will work on it as soon as we fix the HTTP issue.

[Ritesh]

This was just a first release. Definitely, we will improve the text before the final release.

Regarding the second issue, it is strange that it is not working. Maybe we are missing something. We will check upon it on Monday.

[Ritesh]

This is very strange. The error should occur everytime. One thing that I have noticed is that it happens with MySQL 4.0.x and not with v4.1.x. I will research on it even more.

BTW, if the data is not confidential, is there any chance of getting a dump?

[Ritesh]

I think I understood the problem.

v5.1 BETA 3 will have this issue fixed.

[Author]

Posts