[vygi]

peterlaursen wrote on May 3 2006, 09:31 AM:

Another workaround is ….

yes thanks, maybe it ever works for numbers, but remember that there are other problems withour workarounds, eg. wrongly interpreted dates or number as dates in excel (10.05 -> 10th of May 2006) or missing leading zeroes (string '00491634718109' -> number 491634718109) and so on… This makes SQLyog hardly usable, so let's hope one day we will get a real solution.

Regards,

Vygi

[vygi]

peterlaursen wrote on May 3 2006, 08:07 AM:

Create two columns, highligt 2nd column and click the 'insert' button. TWO (and not one) empty rows are created in grid between 1st and 2nd row. This is a GUI bug in my opinion.

Heya,

I always wanted to submit this bug (yes, it is clearly a BUG to me), just did not have time.

Once I've started to create a quite big table and after I had 15 ot 20 rows I tried to insert one right after the first row. I've got two instead like reported here. Then I don't remember what I did exactly but as result I've lost everything as only one column was created in the table.

[vygi]

vygi wrote on Jan 23 2006, 01:20 PM:

Now I still hope that export to Excel via COM will be implemented one day.

I'm sure that our company would purchase 5-licence-pack or so…

Hey here,

now I hope that you didn't forget export to Excel (and other applications) via COM (or whatever…) and one day it will be implemented.

We also have an issue with the float numbers, especially with FLOAT (10,3) as they have three digits after point. MySQL delivers “3” (three) like “3.000” and Excel interprets it as 3000 (three thousand) because of German region settings. This makes things even more difficult. We even had a bad error in our financial reporting because of this!

Vygi

P.S. but we've got a 5-lic.-pack in hope that this issue some time will be fixed

[vygi]

Hey here,

I just wanted to say that I've upgraded to the latest 5.12 beta and still have this boring problem (need to close and re-open all connections every morning after they time out over the night).

[vygi]

addendum:

I have removed my SQLyog, deleted all files from my personal folder and from program files, then installed SQLyog 5.12 Beta2 from the scratch and still have same problem: I need to re-connect manually as soon as connection to the server is lost.

Then I have install an older version (free 5.0 from Oct/Nov 2005) …. and it works just fine! “1053 Server shutdown in progress” pops up only once but after them SQLyog reconnects in the background because I can continue to work on this server (having new connection ID).

After them back to 5.12 Beta — and “2006 MySQL server has gone away” back again 🙁

I don't have any 5.11 beta installers so I was unable to test with them.

Hope it helps,

Vygi

[vygi]

Ritesh wrote on Apr 26 2006, 01:23 PM:

We have not changed any code regarding reconnection. It must be something else. Right now I am in MySQL UC 2006 in Santa Clara and will take a look into it after reaching India on 2nd.

I have anyway asked my developers back in India to reproduce the case but they are unable to.

Is it possible to provide temporary access to your server so that we can check it out?

Hello Ritesh,

thanks for replying!

Unfortunately, all MySQL servers are locatedin our intranet and it doesn't have any connections from outside.

It is possible that something happened while upgrading of SQLyog?

Should I try to make fresh installation or try something else?

There were guaranteed no changes on the server side (and I use at least 4 diferent MySQL servers).

Vygi

[vygi]

peterlaursen wrote on Apr 25 2006, 08:45 AM:

I have two local and two remote servers i can connect to with HTTP-tunnel. And I don't have this issue. Do you have a chabce to conect to some other server, just to find out if the problem is related to one specific server or the problems shall be found on the client side?

Hey ,

yesterday you said “I'll have to reconnect maually” and today “don't have this issue”, so what is right please?

I have at least 4 “local” servers here (1x MySQL5 and 3x MySQL4) and this is definitive a client-side problem (new since some late 5.1 beta).

[vygi]

Same problem with 5.12 BETA2:

– start some SELECT * FROM big_table ORDER BY unindexed_field LIMIT 10;

– switch to another client, make SHOW PROCESSLIST and kill this SELECT query;

– this error message will appear once: “Error No. 1053 Server shutdown in progress”

– this error message will appear every time as long as you don't manually reconnect:

“Error No. 2006 MySQL server has gone away”.

Sorry but it makes 5.11 RC2 and 5.12 BETA2 barely useful to me as our MySQL server has often locked tables and it is not always possible to kill a query from SQLyog (we have to do it via commandline client). And because of time out we have now to reconnect manually next business day at the latest.

[vygi]

peterlaursen wrote on Apr 24 2006, 03:52 PM:

I am not sure about details (hard to remember everything) – if there is a change or not. Ritesh must tell.

There MUST be a change.

Today I came into the office and I must manually reconnect to all MySQL severs because of time out over the night.

It was never needed before!!

It's really boring because I have to save all changed queries as otherwise it will be lost (I have to close and re-open every connection).

I will try 5.12 BETA2 now and will be back with my complaints if it also needs manual reconnect.

[vygi]

peterlaursen wrote on Apr 24 2006, 03:26 PM:

With 5.11 FINAL I get (doing the same exercise)

Error Code : 2006

MySQL server has gone away

(0 ms taken)

and nothing more. Not the popup 'Connection was lost'. I'll have to reconnect maually.

I don't care about “Connection was lost” message which pops up in some cases (sometime it was only shown in the message tab).

I basically ask whether manual reconnection is really necessary in that case?

I am pretty sure that some time ago SQLyog was reconnectic automatically (like eg. the standard mysql CLI client is doing).

Mysql thread killing may be the only option in some cases, eg. when some big table is locked in MySQL4 and “show table status” cannot be executed. I this case, SQLyog hangs when you try to change the database.

The latest SQLyog now needs manual reconnection when connection to the sever is lost and that is really annoying.

[vygi]

I don't know if it is already an answer but on Friday everything was fine; RC2 was stable. Thanks.

[vygi]

Quote:

RC3 at http://www.webyog.com/forums/index.php?sho…65533;entry9745 fixes this issue. Can you confirm it?

Yes it works now: in same table it uses the PK only.

peterlaursen wrote on Apr 21 2006, 12:16 AM:

@Vygi — comments? Can you create a definition and a sequence of SQL's generating an error when there is no PK ? (With a PK it should not be possible now)

I have removed primary keys from the table I have and can't update anything anymore because of float in WHERE. I connot explain why you can'r reproduce it…. Maybe try this before updating:

Code:

UPDATE pladder SET f=1/7

[vygi]

Ritesh wrote on Apr 20 2006, 01:33 PM:

Can somebody confirm the bug fix?

I have installed RC2 and use it but it may take some time (several days) until I can give some feedback.

Last time I have used RC1 without any problems one whole day and next day it crashed twice.

[vygi]

Ritesh wrote on Apr 19 2006, 03:06 PM:

Let me know how it goes. If its not crashing for you without the Virtual Dimension then I guess there is compatibility between SQLyog and the product. We will need to look into it.

I have switched Virtual Dimension off before lunch and worked without it for 3-4 hours but it crashed (silently disappeared) again few minutes ago.

Actually I have following applications running:

– Servan Salamander file manager

– PHPEdit PHP IDE

– 5 PuTTY sessions

– Opera web browser

– Notepad++ text editor

– MS Excel

I had SQLyog with two connections to the same MySQL 5 server and have manually executed lots of small queries like find non-existing entry in one table, verify it in another, and copy it to the first table. There were permanently 3-4 query editor tabs and result grid with very small resultset (empty result or 1-2 short rows).

SQLyou went away when I have switched from it to the text editor and then to one of the PuTTY sessions in order to copy & paste something into the Linux shell. Again, I did not realized when exactly it happened. SQLyog simply wasn't here anymore. No crash reports, just disappeared…. 🙁

Note that I did not have such problems with several SQLyog versions, up to 5.0 final.

[vygi]

peterlaursen wrote on Apr 19 2006, 11:48 AM:

Crazy problems. In this situation we'll have to be sure that it is not the Virtual Dimension porgram that causes this. Do you have a chance to work without it for a period? I have installed it myself and see if something shows up.

yes I have disabled it now, let's see.

BTW I use it since last summer and never had any problems with any application, also not with SQLyog 4.x and 5.0. Only 5.1 betas and RC tend to disappear.

peterlaursen wrote on Apr 19 2006, 11:48 AM:

I think that I remember that your PC at work has an integrated Intel graphics chip?

Yes that's true.

A very standard office PC with some Pentium 4 and Intel graphics.

[Author]

Posts