[Ritesh]

Can you send me some sample data to reproduce the problem?

[Ritesh]

Are you using Create Bulk Insert Statements?

[Ritesh]

Which database you are trying to import data from?

Can you send us sample data and the corresponding XML file? I dont want to guesstimate on the problem.

The problem seems to be with DEFAULT value assigned to columns.

[Ritesh]

Quote:

Yes! I understand that I can do an Import. But I would like to do an automatic sync every 15 minutes or so so i can do this for a kind of insurance if the primary server goes down.

You can schedule SJA to run between any time intervals.

Did you try out the TRIGGER option in SQLyog ODBC Import Tool? You can use it in conjunction with WHERE clause to incorporate SYNC feature between MS SQL and MySQL.

You should read the article as posted by Peter Laursen. BTW, Peter is our in house data sync and ODBC Import expert. He will be more then happy to help you out with your problems.

Quote:

(and the need for the backup was that I tested sqlYog and accidentally destroyed my production database… thats how newbies with sqlyog can “misuse it”..)

I am not sure if I understood the problem. Can you explain it a little more?

[Ritesh]

katla wrote on Oct 5 2005, 09:39 PM:

Its a Great tool by the way!  Would be even greater if you could find a way to do a table sync between a MS Sql server 2005 express and a MySQL server..

[post=”7437″]<{POST_SNAPBACK}>[/post]

You can indeed do it using the ODBC Import Tool (Migration Toolkit in v4.2 BETAs).

[Ritesh]

Problem understood <_< SQLyog checks whether there is any string under NULL column or not. MySQL versions < 5.0 used to have YES and BLANK STRINGS for NULL and NOT NULL value respectively.

MySQL versions > 5.0 seems to have NO explicitly to define columns having NOT NULL property and thus the errors.

This issue affects multiple features of SQLyog. I have asked my developer to look into the issue.

Will be fixed in one of the future BETAS of v4.2.

[Ritesh]

I have added this issue in the TO-DO list.

We will fix this issue in one of the next v4.2 BETAS.

[Ritesh]

http://www.webyog.com/forums/index.php?sho…63&st=0&p=7439&#038;

BETA 5 has the fix for the HTTP Tunneling issue.

Quote:

Error No. 1064

You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version

for the right syntax to use near 'DEFAULT CHARSET=ujis' at line 5

This is because you are running v4.1 or above at your local machine. These MySQL versions support CHARSET options where as v4.0 and below does not. SQLyog uses MySQL's inbuilt CREATE TABLE SQL to generate & copy table structure from one database to another.

If you note, the CREATE TABLE statement in v4.1 and above have CHARSET information included in it and thus the query fails in older MySQL versions.

What you can do now is to use Structure Sync Tool to generate the SQL scripts and remove all the charset information from it. Execute the scripts again at your remote server.

[Ritesh]

Nope.

We are working on some issues regarding log and session file.

I will post in this thread once we release SJA with a fix.

[Ritesh]

Thanks. I will work upon it in some time 🙂

Still feeling lethargic from yesterday's fever :huh:

[Ritesh]

Quote:

Ritesh was it a bug with SQLyog in your opinion that has been fixed, or is it a workaround for diversities in SQL-dialects that have been implemented ?

Its not a bug nor a workaround. Its an improvement in SQLyog Migration Toolkit 😀

Even in MySQL versions < 5.x, an auto_increment column with a default value does not make sense. MySQL < 5.x was less strict and thus the queries worked. It will not in v5.x. From v4.2 BETA 5, SQLyog will not issue a DEFAULT statement when its an auto_increment column.

Quote:

Shawn's own problem is 'NULL as a default value'. Not necessessarily 'NULL as a default value for auto_increment columns'.

You can have NULL as deafult value and it works. I dont think this was a problem with other columns.

BTW, can somebody mail me the XML file? I didnt receive it in [email protected]

[Ritesh]

Has been fixed in BETA 5.

The problem arises when SQLyog specifies a DAFAULT value with auto_increment column and NULL as a default value.

[Ritesh]

Can you post some screenshots?

[Ritesh]

Quote:

save query scripts

Write a query and use File->Save

[Ritesh]

Thanks 🙂

I think SQLyog is specifying DEFAULT value for auto_increment column. This option is not supported in v5.x and also does not make sense.

BETA 5 will fix it where it will not specify DEFAULT value on auto_increment column.

[Author]

Posts