[peterlaursen]

🙁 ouch … this one is almost as bad as the one named Windows …

Nice that you returned to tell this!

[peterlaursen]

Confirmed fixed with beta3:

/* Alter table in Second database */

alter table `test5`.`categorias`

drop column `id`,

drop key `PRIMARY`;

/* Alter table in Second database */

alter table `test5`.`dolar`

change `id` `id` tinyint(4) NOT NULL DEFAULT '0' first,

change `dhora` `dhora` timestamp NULL DEFAULT CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP after `dolar`,

drop key `PRIMARY`;

/* Alter table in First database */

alter table `ferret`.`categorias`

add column `id` int(10) unsigned NOT NULL auto_increment after `descr`,

add PRIMARY KEY (`id`);

/* Alter table in First database */

alter table `ferret`.`dolar`

change `id` `id` tinyint(4) unsigned NOT NULL auto_increment first,

change `dhora` `dhora` timestamp(14) NULL after `dolar`,

add PRIMARY KEY (`id`);

[peterlaursen]

It has worked before!

Now some 5.1.x versions have used 'set names' others 'set character_set_connection'

As long as the client code does not support multibyte chars I think it should only

'set character_set_connection' and NOT 'set names'

I think this illustrates this:

Code:

set names 'latin1';
set character_set_connection = 'ucs2';
show variables like '%character%';
/*
Variable_name Value
———————— —————————————————-
character_set_client latin1
character_set_connection ucs2
character_set_database latin1
character_set_results latin1
character_set_server latin1
character_set_system utf8
character_sets_dir C:ProgrammerMySQLMySQL Server 4.1sharecharsets/
*/

set character_set_connection = 'latin1';
/*
Error Code : 1115
Unknown character set: ''

now reconnecting */

set names 'latin1';
set character_set_results = 'ucs2';
show variables like '%character%';
/* empty set
now reconnecting*/

set names 'latin1';
set character_set_client = 'ucs2';
show variables like '%character%';
/*
Error Code : 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 'show variables like '%character%'' at line 1
*/

[peterlaursen]

I have now written-up quite a lot of our FAQs to reflect the changes with SQLyog 5.1.x.

Please drop a note if I overlooked something that must also be rewritten!

[peterlaursen]

Done:

http://webyog.com/faq/30_106_en.html

[peterlaursen]

Working with locals 4.0.27 and 4.1.19:

If I add a 'Tablename1' in 4.0.27 I get

/* Alter table in Second database */

alter table `ferret`.`categorias`

add column `id` int(10) unsigned NOT NULL auto_increment after `descr`,

add PRIMARY KEY (`id`),

/* Alter table in Second database */

alter table `ferret`.`dolar`

change `id` `id` tinyint(4) unsigned NOT NULL auto_increment first,

change `dhora` `dhora` timestamp(14) NULL after `dolar`,

add PRIMARY KEY (`id`),

/* Create table in Second database */

create table `ferret`.`tablename1` (

`id` bigint(20) unsigned NOT NULL DEFAULT '0' ,

PRIMARY KEY (`id`)

)Engine=MyISAM;

/* Alter table in First database */

alter table `test5`.`categorias`

drop column `id`,

drop key `PRIMARY`,

/* Alter table in First database */

alter table `test5`.`dolar`

change `id` `id` tinyint(4) NOT NULL DEFAULT '0' first,

change `dhora` `dhora` timestamp NULL DEFAULT CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP after `dolar`,

drop key `PRIMARY`,

If I add a 'Tablename1' in 4.1.19 I get

/* Alter table in Second database */

alter table `ferret`.`categorias`

add column `id` int(10) unsigned NOT NULL auto_increment after `descr`,

add PRIMARY KEY (`id`),

/* Alter table in Second database */

alter table `ferret`.`dolar`

change `id` `id` tinyint(4) unsigned NOT NULL auto_increment first,

change `dhora` `dhora` timestamp(14) NULL after `dolar`,

add PRIMARY KEY (`id`),

/* Alter table in First database */

alter table `test5`.`categorias`

drop column `id`,

drop key `PRIMARY`,

/* Alter table in First database */

alter table `test5`.`dolar`

change `id` `id` tinyint(4) NOT NULL DEFAULT '0' first,

change `dhora` `dhora` timestamp NULL DEFAULT CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP after `dolar`,

drop key `PRIMARY`,

/* Create table in First database */

create table `test5`.`tablename1` (

`id` bigint(20) unsigned NOT NULL DEFAULT '0' ,

PRIMARY KEY (`id`)

)Type=MyISAM;

— Where did the 'DROP table TableName1' go when syncing from DB without TableName1 to the one with?

— Looks like the tool does not realize that is has finished …

[peterlaursen]

And I have now given you direct access with all available priv's to the test database there.

And sent you a mail with connection details.

[peterlaursen]

Now .. I synced from to remote 4.0.26 to a local 4.0.27 .. no problem.

Next started 4.0.27 and and 4.1.19 on each their port on the same computer and sync yields (with direct connection to both):

/* Alter table in Second database */

alter table `test5`.`categorias`

drop column `id`,

drop key `PRIMARY`,

/* Alter table in Second database */

alter table `test5`.`dolar`

change `id` `id` tinyint(4) NOT NULL DEFAULT '0' first,

change `dhora` `dhora` timestamp NULL DEFAULT CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP after `dolar`,

drop key `PRIMARY`,

/* Alter table in First database */

alter table `ferret`.`categorias`

add column `id` int(10) unsigned NOT NULL auto_increment after `descr`,

add PRIMARY KEY (`id`),

/* Alter table in First database */

alter table `ferret`.`dolar`

change `id` `id` tinyint(4) unsigned NOT NULL auto_increment first,

change `dhora` `dhora` timestamp(14) NULL after `dolar`,

add PRIMARY KEY (`id`),

[peterlaursen]

@ritesh

both upeters and I tested with a remote 4.0.26 Linux server without tunnel.

As I wrote the data are available at surftown.dk ..

Server here is '4.0.26-standard-log' on GNU/Linux

It does not happen with tunnelling …

(and still reproducable .. now with a 5.0.21 running at local)

With HTTP-tunnelling;

/* Alter table in Second database */

alter table `jazcyk_test`.`categorias`

drop column `id`,

drop key `PRIMARY`;

/* Alter table in Second database */

alter table `jazcyk_test`.`dolar`

change `id` `id` tinyint(4) NOT NULL DEFAULT '0' first,

change `dhora` `dhora` timestamp NULL DEFAULT CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP after `dolar`,

drop key `PRIMARY`;

Without tunnel:

/* Alter table in First database */

alter table `ferret1`.`categorias`

add column `id` int(10) unsigned NOT NULL auto_increment after `descr`,

add PRIMARY KEY (`id`),

/* Alter table in First database */

alter table `ferret1`.`dolar`

change `id` `id` tinyint(4) unsigned NOT NULL auto_increment first,

change `dhora` `dhora` timestamp(14) NULL after `dolar`,

add PRIMARY KEY (`id`),

@Ritesh .. mail me your ip and I can arrange direct acces to surftown …

[peterlaursen]

It is better that you create a 'ticket' .. we can then better coordinate!

http://www.webyog.com/support/ttx.cgi

But I can test with the same versions! Will do!

Do you use tunnelling to the remote host ?

Write-up:

Issue confirmed:

4.0.26 remote and 4.1.19 local, no tunnelling!

/* Alter table in Second database */

alter table `jazcyk_test`.`categorias`

drop column `id`,

drop key `PRIMARY`,

/* Alter table in Second database */

alter table `jazcyk_test`.`dolar`

change `id` `id` tinyint(4) NOT NULL DEFAULT '0' first,

change `dhora` `dhora` timestamp NULL DEFAULT CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP after `dolar`,

drop key `PRIMARY`,

/* Alter table in First database */

alter table `ferret`.`categorias`

add column `id` int(10) unsigned NOT NULL auto_increment after `descr`,

add PRIMARY KEY (`id`),

/* Alter table in First database */

alter table `ferret`.`dolar`

change `id` `id` tinyint(4) unsigned NOT NULL auto_increment first,

change `dhora` `dhora` timestamp(14) NULL after `dolar`,

add PRIMARY KEY (`id`),

@ritesh+@sarat: data (ferrets-remote.sql) available at surftown.dk (MySQL 4.0.26)

[peterlaursen]

So what do we do from here ??

[peterlaursen]

Weird.

Looks like an issue with my 'Download Manager' then.

After import and compare .. 'copy to clipboard' or 'save to file' I get:

One way:

/* Alter table in Second database */

alter table `ferret2`.`categorias`

drop column `id`,

drop key `PRIMARY`;

/* Alter table in Second database */

alter table `ferret2`.`dolar`

change `id` `id` tinyint(4) NOT NULL DEFAULT '0' first,

drop key `PRIMARY`;

the other way:

/* Alter table in First database */

alter table `ferret1`.`categorias`

add column `id` int(10) unsigned NOT NULL auto_increment after `descr`,

add PRIMARY KEY (`id`);

/* Alter table in First database */

alter table `ferret1`.`dolar`

change `id` `id` tinyint(4) unsigned NOT NULL auto_increment first,

add PRIMARY KEY (`id`);

[peterlaursen]

To me it looks as something went wrong with that upload.

I get a weird file down!

Are you sure that the upload finished?

[peterlaursen]

You will need to use the DELIMITER syntax – with SQLyog and cmd-line as well.

With SQLyog the syntax is for instance

DELIMITER $$;

CREATE FUNCTION hello (s CHAR(20))

RETURNS CHAR(50)

BEGIN

RETURN CONCAT('Hello, ',s,'!');

END $$

DELIMITER ;$$

Note that 'DELIMITER' is not an SQL statement and is not understood by the server – it is implemented in the client only, and no 'DELIMITER ..' will ever reach the server (and if it does it raises an error).

From version 5.0 SQLyog supports DELIMITER

'DELIMITER …' changes the DELIMITER to be used between SQL-statements so that ';' can be used inside the ROUTINE.

[peterlaursen]

Thanks for your suggestion.

Actually sorting and filtering options as well as a GUI query-builder feature is planned for the future.

The FILTER is a little more complicated than LIMIT as we'll need a way to specify whether is should apply to a single column or all colums. We are looking at Office-suite databases etc. for inspiration.

[Author]

Posts