[vygi]

Looks similar to my issue from the prevous thread: http://www.webyog.com/forums//index.php?showtopic=3274

I also had “Österreich” in the table but just “sterreich” on the screen.

Could you please tell us which MySQL version is used (5 or 4/4.1), and if the problem can be (temporarily) fixed by restarting of SQLyog (or starting of new instance)?

[vygi]

surprise: I have opened another, new SQLyog instance, and it works correctly!

UTF8 vs. non-UTF handling seems to be “broken” in my first SQLyog, which is running now for 3 days or so.

[vygi]

peterlaursen wrote on Jun 6 2007, 09:46 AM:

please tell – how do yo uexecute queries simultaneously?  From different connection windows?

So I have two servers with two huge databases, and two connection windows to them.

1: I start query A on server A. It takes let's say 2 minutes

2: 30 sec later I switch to connection B and start query B on server B; it takes 5 minutes.

Now I have to wait 5 minutes until the B query is finished. SQLyog does remains “busy” on A connection until then, although query A finishes in between.

I saw that there is no such problem if A query takes longer and B is quick.

[vygi]

peterlaursen wrote on Jun 6 2007, 09:42 AM:

yes .. SQLyog 6 can handle non-unicode data – or at least it should!

I still think your server is a 4.0 ?

In my case it's 5.0.40 Enterprise.

Let me know how can I/we debug and fix this vehaviuor, otherwise I have to uninstall yog 6.0 ASAP.

[vygi]

I am susing one of the latest MySQL 5 versions (5.0.40) but am very confused with all these UTF8 features of SQLyog 6, and these issues forces me to uninstall it and replace it again by SQLyog 5.

EXAMPLE:

I have a small table with country names; one of them is Österreich (Autria) in name field with latin1_german_ci collation.

SELECT statement via mysql CLI returns correctly “Österreich”.

SELECT via SQLyog 6 returns “sterreich” (!) without “Ö”.

OK… I have put “Ö” in front of the name manually .

Now SELECT via SQLyog 6 returns “Österreich” but mysql CLI and all PHP scripts read it “Ãsterreich” for some reason!!

Similar with “Åland Islands”: either “Åland” via CLI but “land” via SQLyog or “Åland” via SQLyog but “Ã

land” (yes: with carriage return after 1st character) via CLI.

Can SQLyog 6 correctly handle non-UTF databases at all?!…

[vygi]

peterlaursen wrote on Jun 6 2007, 08:37 AM:

OK .. we will have to test more in depth too.

but repainting in the RESULT tab involves Win32 API calls.  So I just wondered if it was Windows itself who 'waited'.

Don't know… but it would be strange if Windows would wait several minutes to repaint.

Note that in same time I can easily switch to any other application with no problems.

I also can open new (let's say the 3rd) connection (Ctrl-M dies not work but “File / New Connection…” does) and perform here new queries with absolutely no delays. In the meantime, 1st SQLyog connection (with long ago finished query) will still wait for the 2nd.

[vygi]

peterlaursen wrote on Jun 5 2007, 01:39 PM:

is this a new issue with version 6.0, or did you only get across that recently?

I am not sure about it but I think I have sometimes experienced it before.

peterlaursen wrote on Jun 5 2007, 01:59 PM:

In 'the first shot' we cannot reporduce this.  Every query displays when finished and other queries are running.

I wonder if your system is getting close to full memory use?

My PC has 512 MB physical memory, 70MB are free right now, but it often uses some virtual memory as I run many parallel processes.

I don't see any significant slow-down, though.

Looks like it only happens when the 2nd query takes longer than the 1st one:

If I start 1st and then 2nd — SQLyog displays 2nd result and continues with 1st if 2nd is quicker, but waits for 2nd if 1st is faster.

I hope I can test more today.

[vygi]

peterlaursen wrote on May 30 2007, 11:55 AM:

An ALTER TABLE taking 20 minuts to complete. Why that much?

ALTER TABLE takes 20 minutes just because the table currently has 105,332,842 rows!! 🙄

Data file is about 1.3 GB and index 2.7 GB (yep that's right: index is much bigger than data).

The structure was very simple, just two columns, one int and another mediumint, plus two indexes.

ALTER TABLE has added 3rd column, a tinyint, with no index.

By the way, our biggest table has over 43 GB of data, and ALTER TABLE would take at least 3 hours 😛

[vygi]

P.S. I have killed this SQLyog RC1 process and am about to install RC2 to see if it's any better.

[vygi]

Any news on this please??

Were there any changes in Release Candidate 2 (RC2)?

Few days ago I have installed RC1, and today it again became crazy: look at the screenshot!

It happened right after ALTER TABLE which took maybe 20 minutes.

Vygi

[vygi]

peterlaursen wrote on May 14 2007, 11:25 AM:

we have 'vacuumized' the program for all sorts of leaks. However I doubt we will be able to release beta5 today. We need to finish some in-depth testing with data sync. We are a little low on manpower due to some persons being sick

Thanks for the info; no hurry! Take your time (but keep it goin')

Best wishes (and “Get well soon” to somebody…)…

Vygi

[vygi]

Any news on this topic please???

I have to restart SQLyog because of this bug every second day.

[vygi]

peterlaursen wrote on May 10 2007, 08:26 AM:

It is fixed in both the 5.x and 6.x development tree now.

Are you asking for a 5.x or 6.x build? We can give a 5.31 'not-releeased' and hope to release 6.0 beta 5 tomorrow.

Is it community/trial/enterprise you need?

I did not have any problems with previous 5.x versions and none of my workmates have any issues with it but I'm using 6.0 beta 4 at the moment. So no need for any special 5.31, I will wait until tomorrow and install the bets 5 then. Thanks!

[vygi]

Yes, it happens with MySQL 4.

Is there a chance to get a fixed version soon?

Because I can't use this SQLyog with our older server….

[vygi]

peterlaursen wrote on Apr 25 2007, 02:10 PM:

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!

sorry; I was posting in “BETA Discussions”, and every 6.0 Beta is affected. But I promise to indicate exact SQLyog version every time, sir! 😉

[Author]

Posts