Structure Synchronization Tool Bugs

[sommerjack]

Hello,

I am using SQLyog Enterprice v6.05 and have experienced some bugs when using the Structure synchronization tool.

1) When copy Sync SQL to Clipboard the charset is shown like CHARSET='uft' and NOT CHARSET='utf8';

Example:

/* Alter table in Second database */

alter table `accountno`

change `accountNo` `accountNo` varchar(20) NOT NULL after `accountNoID`, COMMENT='', DEFAULT CHARSET='utf';

2) When saving Sync SQL to file the data is unreadable…?! Please see enclosed document. Try rename the file to the extension .sql.

3) You can´t alter a table to synchronize it with an external table. It keeps on saying that the two tables are not synchronized with a blue color, even if you make the alter statement from SQLyog or in PHPmyAdmin (the web interface from the hosting company).

The statement below is executed in PHPmyAdmin:

/* Alter table in Second database */

alter table `testimonial`

change `createdDatetime` `createdDatetime` datetime NOT NULL after `testimonial`,

change `userID` `userID` int(11) NOT NULL after `createdDatetime`, COMMENT='';

Query response:

Din SQL-forespørgsel blev udført korrekt (Forepørgsel tog 0.1100 sek)

(Your SQL statement was correct executed (Query took 0.1100 sec) )

– but it stills keep on telling me that the two table are not synchronized?

Can you help me?

[peterlaursen]

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?

[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?

[peterlaursen]

1) ok .. this one is dead!

2) avoid programs with word processing capabilities (like Wordpad) when working with code!

Save the file .. open in Notepad (rightclick .. open with (Danish: højreklik .. åbn med)). I can only repeat that the extension does not change the content of the file. Do you doubleclick on the file? Then of course the associated program will open it. Try open from right-click menu or the program file menu.

Go to control panel … folder setting (Danish: kontrolpanel .. mappeindstillinger). What program is associated with .sql files on your system?

i am pretty sure taht this is definitely an issue with your system or the way you use it!

3)

This is nonsense: “In SQLyog the field errorTimestamp can have a NULL value .. On the SQL server the same field can´t have a NULL value”. There is nothing in SQLyog! SQLyog is a database client – it has no data of its own, everything is in the MySQL database!

What does “SHOW CREATE TABLE ;” return for the table? This is how you do: ask the server with SHOW statements! You seem to believe phpMyAdmin more than you believe SQLyog! Why? They are both clients only! phpMyAdmin is not more 'natural' for MySQL than SQLyog is! The only client that has a special 'status' is the 'mysql' command line client!

Always when you are in doubt: ask the server: “SHOW …” ! (or click on OBJECTS tab in SQLyog)

The 'quotes' from phpMyAdmin and SQlyog are not readable if you never saw the original from where it was copied. You may attach screenshots instead.

BTW: PLEASE … no more phpMyAdmin in Danish! 🙂 Translation is horrible!

And also consider: if by chance I was not Danish, no one would have been able to understand much meaning of your latest post!

[Author]

Posts