[vygi]

peterlaursen wrote on Apr 25 2007, 01:53 PM:

BTW: you do not mind if I move this post to the SQLyog category? 😛

Oooops…. SORRY!

I thought I have posted in “BETA Discussions”, but I was totally wrong 😉

[vygi]

It happened again few minutes ago and I had to restart SQLyog again.

> When you are using the term 'canvas' do you mean that you are using the Query Builder?

> From the screenshots I understand that it is not the case, but please confirm!

no, I don't use query builder.

under “canvas” I just meant SQLyog window.

> Undoubtly some memory corruption. Not sure that this is a SQLyo issues. But likely it is. We will have to look detailed into it.

> Unless you can say that some other program started when problems appeared.

(almost) no other programs in use, just SQLyog. Excel and Opera open too, but I was working only with SQLyog.

> Can you explain what you are doing? In case you experience this again the HISTORY recordings would be valuable?

nothing special, just making JOINed SELECTs, browsing tables, doing some data editing too.

It works fine for a couple of hours, but then gets out of control somehow…

SQLyog version, please? First time you try this version? Or is it the same old version as you always used?

I always try to use the newest; Beta 4 in this case.

[vygi]

peterlaursen wrote on Apr 25 2007, 11:56 AM:

I am afraid I do not fully understand this:

You experience that reconnects fails with this specific server, but normally it works?

Did you experience this once or is it reproducable?

Do you know if the server may have been unreachable for a period of time that night?

I had SQLyog open since yesterday and now I start to copy a table from server A (connection A) to B. Here I get “Mysql Server Gone Away” error because current connection is not valid anymore. I have eg. first to switch between databases on curent server A (to force re-connection).

Some time ago SQLyog has even crashed when connection B (copy table TO) was timed out. This issue has been fixed, and SQLyou reconnects to server B when I try to copy table and connection A is okay but B is not. It just still makes troubles when also A is timed out.

Hope you understand now….

And yes, I can reproduce it:

1: in SQLyog open connection B to server B

2: in SQLyog open connection A to server A

3: in SQLyog focus any database/table you want to copy to B

3: kill connection A in the background (eg. from mysql command line)

4: in SQLyog try to copy table from server A to B –> Mysql Server Gone Away!

[vygi]

ooops…. few minutes later it's totally out of control: result set appears in the left top corner of the screen, on the top of everything; dialog windows are mostly empty and form elements just shortly appear when I move the mouse over them; even the Windows task bar becomes often gray. I have to restart SQLyog as long as it did not crash my whole PC.

[vygi]

larsen wrote on Apr 3 2007, 08:25 AM:

s. attached screenshot

Is already known and submitted: http://www.webyog.com/forums/index.php?showtopic=3129 (not confirmed and no info about possible fix, though)

Glad to see that I am not the only one who has those squares.

[vygi]

peterlaursen wrote on Mar 27 2007, 04:02 AM:

Are there any (LONG)BLOBs in the data that you copied?

Nope; no one single BLOB or TEXT column, only a couple of numbers, datetime fields and varchars.

Also note that memory consumption grows even with every connect/disconnect (I guess, no matter which databases/tables are on server) and on every refresh (F5) of any SELECT query.

Let me know if you have further questions but remember that I have to remove the 6.0 from my PC, so no new info can be provided.

[vygi]

peterlaursen wrote on Mar 22 2007, 11:30 AM:

“We're using German Windows XP Server, SP2”

BTW: this is not a server issues. It happens on the client side alone.

What is the client platform? “German Windows XP Server” = 2003(server) or XP ?

Sorry; I wanted to say “German Windows XP Professional” (not “server”) as workstation,

and I have a standard installation without any special settings or additional languages.

[vygi]

peterlaursen wrote on Feb 19 2007, 05:15 PM:

But 'database does not exist' should not occur if it does exist, of course.

Thanks for the info;

yes, now I also understood when it happens and how to reproduce it.

The reason for the error message is: the statement is being executed when different database is selected.

– change to “second_database” (“use second_database” in the background)

– select something from the first one (select * from first_database.sometable limit 1)

– SQLyog performs “show full fields from sometable” without “use first_database” and without adding “first_database.” in front of the table name, therefore MySQL answers “table second_database.sometable doesn't exist”.

Then it happens also when I click F5 or “Execute Current Query” and don't want to edit query results.

Regards,

Vygi

[vygi]

well… it sounds really weired … because two different connections are mixed up:

this USE statement should be run on another connection and do not affect the first one.

Usually it is speciffic to connection but seems like it does not work like expected when a slow query is running. And everyithing is again OK when it's finished.

Anyway, I second that you should study your own code, as I can't explain what is going wrong here.

[vygi]

oh… thanks a lot! I was not aware of it!

This thing wasn't here back in October when I've tried to find something: “Date Published: 11/6/2006”

[vygi]

Thanks, Peter!

re data export to Excel: I've already posted before that we currently still have Office/Excel 2000 which doesn't support XML.

That's really a shame, sorry!

I had a chance to test it and it worked but we still can't start to use it productively.

We hope to get Office/Excel 2003 in few weeks, though.

Anyway, thank you all for this feature – it's really important to us!

[vygi]

HAPPY NEW YEAR, by the way…

[vygi]

ronjeremy_69 wrote on Dec 29 2006, 06:41 PM:

This has happened to me also on occasion, maybe once a month or two so its not too big of a deal. Rebooting the computer always fixes it.

I have just to restart SQLyog and not the whole computer, so it is somehow SQLyog-related.

Next time I will try to copy/paste using some other program when it happens to see if only SQLyog is affected or everything.

[vygi]

P.S. when someone asks why I need it:

we still have some MySQL 3.x and 4.0 servers and they do not support subselects, so sometimes I need to select IDs by some special query, then copy them to clipboard (seperated by commas) and then make eg. DELETE FROM table WHERE id IN ();

[vygi]

ronjeremy_69 wrote on Dec 21 2006, 06:39 PM:

This wasnt exactly like the old bug, but was close, and is fixed with the latest release.

See this post from last week:

http://www.webyog.com/forums/index.php?showtopic=2760

oops… sorry!! :ph34r:

[Author]

Posts