[peterlaursen]

link is fixed now

[peterlaursen]

This is sprobably because the tables contain data.  And the FK you define are conflicting with the data!

example:

If 'child' (table `orders') has a column CustomerId pointing to the ID column of 'parent' (table `customers`) and if `customers`.`ID` holds the data '1','2','3' and '4' you cannot define a PK if `orders`.`CustomerId` hold other data than  '1','2','3' and '4'.

A Foreing Key is a CONSTRAINT on data.  there can only be data in 'child' that are in 'parent' too.

You could try starting with empty tables!

[peterlaursen]

You cannot join from distinct servers.  SQL does not allow for that!

[peterlaursen]

Code:

Ok, I suppose the WIZARD completed successfully, but the JOB did not!

Yes .. that is what it says!

Obviously you cannot authenticate!

1) Please doublecheck user and password

2) Run the wizard but select to save the jobfile (and not execute).  Are user details in the jobfile OK?

3) Try a 'Notifications Service' job on that server. for instance juste execute 'SELECT'1';” …

Questions:

1) do you use any kind of tunnelling?

2) if not does user have access from remote machines?

[peterlaursen]

Also read: http://webyog.com/faq/11_68_en.html

[peterlaursen]

“NULL definition mismatch for 'date_created' column in '`members`' table”

We did fix several issues with Sync of time/type variables across different MySQLversion between your program version and 5.22.  We are not aware of any issue when syncing 4.1.x to/from 5.0.x

Why don't you try out the TRIAL?

[peterlaursen]

1) No arrow means unsorted.  Data are displayed in the order that they were retrieved from MySQL.

2) Arrow down means that it is sorted ascending and next click will sort descending

3) Arrow up means that it is sorted descending and next click will sort ascending

.. actually I am in doubt myself what is most intuitive!

Note:this sorting will only sort the SQLyog data buffer and not retrieve data from MySQL again.

We will soon provide more advanced more advanced options:

*multiple column sorting

*filtering

*sorting and filtering from the context menu of a cell

and will keep this post in mind when coding it!

[peterlaursen]

It really looks like you did not isntall to the same folder!

How many sqlyog.ini instances are ther on your system?

Those data are stored in the sqlyog.ini file!

If the fille got corrupted for some reason you may have a backup?

[peterlaursen]

I replied in the other thread. <_< BTW: pls only one post per question!

[peterlaursen]

Both the STRUCTURE SYNCHRONIZATION and DATA SYNCHRONIZATION are in ENTERPRISE TRIAL.  Everything is fully identical to ENTERPRISE REGISTERED VERSION except that the TRIAL only lets you sync two tables at a time.

COMMUNITY version does not have any of the SYNCHRONIZATION tools.

[peterlaursen]

Is there a USE statement in your file.  If so the database specified with the USE statement will be USED …

[peterlaursen]

My mistake.  I checked the wrong file.

You are right!

[peterlaursen]

Still the backup 'powertool' of ENTERPRISE version has the option.

the .zip.  

Strange!  we just downloaded and unzipped, and everything is there!

[peterlaursen]

There was a FAQ actually: http://webyog.com/faq/28_139_en.html

This one explains why we chose NOT to let ALTER TABLE create the index

[peterlaursen]

1) With CREATE TABLE SQLyog does everything itself.  

2) With ALTER TABLE you will have to help yourself.

You will need to create an index first on the column that shall be auto-increment.

The reason is a (pretty technical) issue in MySQL with UNIQUE keys and ALTER TABLE .

 and I'll have to vacuumize my memory if I shall remember all details …

An example:

1)

Start using CREATE TABLE GUI to create this:

Code:

CREATE TABLE `keytest` ( `id` bigint(20) NOT NULL auto_increment, `id2` bigint(20) NOT NULL, `t` varchar(20) default NULL,
PRIMARY KEY (`id`),
) ENGINE=InnoDB DEFAULT CHARSET=latin1

2)

Now create an index with MANAGE INDEXES like

Code:

CREATE TABLE `keytest` ( `id` bigint(20) NOT NULL auto_increment, `id2` bigint(20) NOT NULL, `t` varchar(20) default NULL,
PRIMARY KEY (`id`),
KEY `id2` (`id2`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1

3)

ALTER TABLE GUI now lets you define:

Code:

CREATE TABLE `keytest` ( `id` bigint(20) NOT NULL, `id2` bigint(20) NOT NULL auto_increment, `t` varchar(20) default NULL,
PRIMARY KEY (`id`),
KEY `id2` (`id2`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1

With CREATE TABLE however you can go directly to step 3!

Do you use CREATE TABLE or ALTER TABLE?

[Author]

Posts