[sommerjack]

Hello,

I am unable to find the ticket system. Could you send me a link to your ticket system, please?

Or maybe you can send me a link to download SQLyog 7.15 version.

I will answer your questions:

1. What's your OS?

Window XP

2.This crash started when you install/uninstall some application?

I didn´t install or uninstall other applications

3.Check if any installed security related program 'knocks down' SQLyog. Most security suites come with some 'script killer' feature.

I will try to check my security related programs.

4.Could you please attach the dump, so that we can try at our end?

Where can I find the dump? What is the name of the file?

[sommerjack]

peterlaursen wrote on Aug 23 2007, 08:21 PM:

1)

is a known bug that is fixed in 6.06 beta. Please refer to the release notes! (news section of this Forum)

2)

your file is readable for me, except that a lot a SPACES have been inserted. See attachment. What text editor or other program do you paste into before saving? I think it is an issue with that program! Please try Notepad ('Notesblok' in Danish). But of course there are hundreds of text editors where it works. I cannot reproduce the additional SPACES. I also notice that your file is ANSI-encoded. If a file is saved directly from structure sync GUI it is saved as windows 'unicode' (utf16) on my system. That is why i am almost sure that you do not use the 'save' button, or you may have opened and saved the file in some prgram. Maybe you use a program that does not support (utf16) 'unicode'.

But that also surprises me. For portability I think we should save the file as utf8 as we do with all other files since version 6.0! But a 'decent' editor on Windows supports all three: ANSI, UTF8 and UTF16!

3)

please also try if 6.06 beta fixes this (an issue with TRIGGERS was fixed). If not best would be if you attached a structure-only dump (no data required for this) of the database from BOTH servers, zip and attach here (or you can create a ticket if you do not want to expose it in public).

Why should I rename the file to .sql? That does not change the content of the file! If the .txt or .sql extension makes any difference it is an (association) issue with your system only!

BTW: please always tell the MySQL server versions involved! Are you syncing between different MySQL versions? And do you use features supported by one of the servers only?

Alright, first of all thanks for your quick reply. And I think product “SQLyog” is a great tool and the best I have ever tried. My partners who work with databases also praise this product very much.

Regarding point 1:

Yes it works in SQLyog v.6.06. Great 🙂

Regarding point 2:

What text editor or other program do you paste into before saving?

I don´t paste the text into a program, I use the button “Save Sync SQL to File…”. That´s here it goes wrong, not if I paste the statement into the text editors.

If I save the file with the extension .sql, the text is unreadable.

If I rename the file as .txt I can read the sql statements, but there is no linebreak. Comments are unreadable here.

I have tried notepad (Notesblok) and Wordpad, the Danish edition.

Regarding point 3:

On my local machine I use mySQL Server 5.0.

On the external server I am using mySQL server version: 4.1.20

Okay I made a mistake here. If I copy several sql statements into the query window in SQLyog I have to mark all the statements or push the button “Execute all queries”. I forgot that. That was my mistake. That is why only the first statement was executed.

But some field attributes are not shown correct in SQLyog, i.e.:

In SQLyog the field errorTimestamp can have a NULL value:

Field Type Collation Null Key Default Extra Privileges Comment

---

---

---

---

---

---

---

---

---

errorID int(11) NULL PRI (NULL) auto_increment select,insert,update,references

errorTimestamp timestamp NULL YES

On the SQL server the same field can´t have a NULL value:

Feltnavn Datatype Kollation (Collation) Attributter Nulværdi Standardværdi Ekstra Handling

errorID int(11) Nej – auto_increment Gennemse bestemte værdier Ændre Slet Primær Unik Indeks Fuldtekst

errorTimestamp timestamp – – Nej CURRENT_TIMESTAMP

Is that a SQLyog bug or because the two mySQL server are two different versions?

[sommerjack]

peterlaursen wrote on Aug 8 2007, 11:29 AM:

In 5.19 there is a charset collector in the connections screen. What do you select here and what is server default charset?

Thanks for your support and questions 🙂 Now it works.

I didn´t realized until now that there was a charset collector in the connections screen… Now I changed this to Latin1 and it works now.

Another thing is that when I save a new table it is automatically stored with table type InnoDB. How can I change the settings so it will be saved as a myISAM?

[Author]

Posts