[peterlaursen]

confirmed!

the position of the horisontal divider between editor and DATA area is not saved

– the vertical divider between Object Browser and the rest is.

[peterlaursen]

This looks like czech or slovak ?!

'latin2' should work.  Or one of those: http://dev.mysql.com/doc/refman/5.0/en/charset-ce-sets.html

but give us about 3 weeks and the first 5.3 beta with full unicode support will be released.  Then you will not have to bother as all as long as the server is 4.1 or higher.

[peterlaursen]

Please try this:

http://www.webyog.com/downloads/betas/not_…QLyog523Ent.exe

With this build we have reversed the order or INSERTs, UPDATES and DELETES.

It will now perform those in the order DELETE -> INSERT -> UPDATE.

This will ensure that if some 'trigger code' in some application changes data (typically a 'counter' row) while the sync is running (between DELETEs and INSERTs) the target database will still have all rows existing on the source at the time the last checksum was collected.

It may display a log message like

Code:

DELETES INSERTS UPDATES
============================
37    42         7

.. in case that such 'trigger code' has been active (also if there actually was nothing to be deleted on target). Actually the rows affected will first be DELETEd on the target and next the updated row on source will be INSERTEd on target. So with this example this 'application trigger code' was active on 37 rows while the sync was running and 5 new rows and 7 updated rows were found.

[peterlaursen]

my mistake!

You cannot use the “>” character for redirecting the output from SJA.  SJA is not a console.

You must “SELECT … INTO OUTFILE … “.  This will save on the client machine!  But if you SJA is running on the same machine as the server it is the same thing.

If you use windows filenames do not forget to escape the backslash character like:

Quote:

select … into outfile 'c:\pic.gif' from `thetable` where …. ;

On Linux it would be like

Quote:

select … into outfile '/home/me/mygifs/pic.gif' from `thetable` where …. ;

And I think you should upgrade SJA, not for this simple query but because a lot of bugfixes in between the versions.

[peterlaursen]

basically SQLyog (as any MySQL client) will have to send an SQL statement like

UPDATE {what to update} WHERE {where-clause}.

1) If there is a Primary key this one will be use in the where-clause

2) If there is no Primary key the where-clause will be like 

WHERE col_1 = 'value-1' and col_2 = 'value_2' … and col_n = value_n.

However BLOB/TEXT types are generally omitted in the WHERE because they can hold very long data.

You could also have added a Primary Key to the table.

[peterlaursen]

“When I try to create a table that has uppercase characters SQLyog converts them to lowercase.”

NO!!! Absolutely NO!!! The MySQL server does!

“The only way to get uppercase is to go to the data directory in the MySQL installation directory and change the name there.”

My advice: do not mess around with MySQL this way!

You should set the “lower_case_table_names” system variable = 2 in server configuration!

refer to: http://dev.mysql.com/doc/refman/5.0/en/ide…ensitivity.html

However also read this:

http://webyog.com/faq/35_25

… there is a bug with some MySQL versions affecting InnoDB tables when the server is running on Windows!

[peterlaursen]

Please read:

http://webyog.com/faq/28_70_en.html

I think the reason is that you use TEXT (or BLO:cool: variables to store your strings ?

It is a common misunderstanding by 'fresh' MySQL users to use TEXTs.

Maybe because programs like MS-access use the type name 'text' for string data.

You should preferably use (var)char for storing strings unless you really need the full size of a TEXT/MEDIUMTEXT/LONGTEXT. 

MySQL docs: http://dev.mysql.com/doc/refman/5.0/en/str…e-overview.html

[peterlaursen]

fixed in the development tree.  Beta 2 with the fix will be released tonight or tomorrow.

[peterlaursen]

I can easily reproduce the error with the mysql.proc does not exist.  See attached.  I

just renamed to table.Do not ask us sfor help with that.  Ask your SysAdmin to fix that mysql installation instead.  It is sick and needs some medicine .. go to the MySQL doctor and get a recipe on some “mysql_fix_privilege_tables.sql” 😉

When the databases/servers are OK the STRUCTURE SYNC tool generates this SYNC script:

/* Create table in First database */

create table `mysql_bdhockey`.`chatroom` (

`crid` int(11) NOT NULL auto_increment ,

`nid` int(11) NOT NULL DEFAULT '0' ,

`poll_freq` int(2) NOT NULL DEFAULT '3000' ,

`idle_freq` int(3) NOT NULL DEFAULT '60000' ,

`kicked_out_message` longtext NULL ,

`banned_message` longtext NULL ,

`module` varchar(255) NULL DEFAULT 'chatroom' ,

`auto_archive` int(1) NULL DEFAULT '0' ,

`old_msg_count` int(3) NULL DEFAULT '20' ,

`modified` int(11) NOT NULL DEFAULT '0' ,

PRIMARY KEY (`crid`) ,

KEY `nid` (`nid`)

)Engine=MyISAM;

/* Create table in First database */

create table `mysql_bdhockey`.`chatroom_ban_list` (

`crid` int(11) NOT NULL auto_increment ,

`uid` int(11) NOT NULL DEFAULT '0' ,

`admin_uid` int(11) NOT NULL DEFAULT '0' ,

`modified` int(11) NOT NULL DEFAULT '0' ,

KEY `crid_uid` (`crid`,`uid`)

)Engine=MyISAM;

/* Create table in First database */

create table `mysql_bdhockey`.`chatroom_chat` (

`ccid` int(11) NOT NULL auto_increment ,

`crid` int(11) NOT NULL DEFAULT '0' ,

`uid` int(11) NOT NULL DEFAULT '0' ,

`chatname` varchar(255) NOT NULL ,

`modified` int(11) NOT NULL DEFAULT '0' ,

`when_archived` int(11) NULL ,

PRIMARY KEY (`ccid`) ,

KEY `crid` (`crid`) ,

KEY `modified` (`modified`)

)Engine=MyISAM;

/* Create table in First database */

create table `mysql_bdhockey`.`chatroom_chat_invites` (

`cciid` int(11) NOT NULL auto_increment ,

`sender_uid` int(11) NOT NULL DEFAULT '0' ,

`invitee_uid` int(11) NOT NULL DEFAULT '0' ,

`declined` int(1) NULL ,

`created_ccid` int(11) NULL ,

PRIMARY KEY (`cciid`) ,

KEY `sender_uid` (`sender_uid`) ,

KEY `invitee_uid` (`invitee_uid`)

)Engine=MyISAM;

/* Create table in First database */

create table `mysql_bdhockey`.`chatroom_msg` (

`cmid` int(11) NOT NULL auto_increment ,

`ccid` int(11) NOT NULL DEFAULT '0' ,

`uid` int(11) NOT NULL DEFAULT '0' ,

`msg_type` varchar(64) NOT NULL ,

`msg` longtext NOT NULL ,

`session_id` varchar(255) NOT NULL ,

`recipient` varchar(255) NOT NULL ,

`modified` int(11) NOT NULL DEFAULT '0' ,

PRIMARY KEY (`cmid`) ,

KEY `ccid` (`ccid`) ,

KEY `session_id` (`session_id`) ,

KEY `recipient` (`recipient`) ,

KEY `modified` (`modified`)

)Engine=MyISAM;

/* Create table in First database */

create table `mysql_bdhockey`.`chatroom_msg_archive` (

`cmid` int(11) NOT NULL DEFAULT '0' ,

`ccid` int(11) NOT NULL DEFAULT '0' ,

`uid` int(11) NOT NULL DEFAULT '0' ,

`msg_type` varchar(64) NOT NULL ,

`msg` longtext NOT NULL ,

`session_id` varchar(255) NOT NULL ,

`recipient` varchar(255) NOT NULL ,

`modified` int(11) NOT NULL DEFAULT '0' ,

PRIMARY KEY (`cmid`) ,

KEY `ccid` (`ccid`) ,

KEY `session_id` (`session_id`) ,

KEY `recipient` (`recipient`) ,

KEY `modified` (`modified`)

)Engine=MyISAM;

/* Create table in First database */

create table `mysql_bdhockey`.`chatroom_online_list` (

`coid` int(11) NOT NULL auto_increment ,

`ccid` int(11) NOT NULL DEFAULT '0' ,

`uid` int(11) NOT NULL DEFAULT '0' ,

`session_id` varchar(255) NOT NULL ,

`guest_id` int(11) NOT NULL DEFAULT '1' ,

`away` int(1) NULL DEFAULT '0' ,

`is_admin` int(1) NULL DEFAULT '0' ,

`modified` int(11) NOT NULL DEFAULT '0' ,

PRIMARY KEY (`coid`) ,

KEY `update_time` (`ccid`,`uid`,`session_id`)

)Engine=MyISAM;

.. what is what it should.  Right?? After execution of the script next sync does not report any difference.

Apart from the problem(s) with your server/host, what is then the porblem?  Please explain!

[peterlaursen]

sorry .. I did not notice the version number in the header.

And I suppose that you manualy select “cp1251” in the dropdown when connecting?

Now the first beta supporting unicode is only a few weeks away, so we most likely won'

t fix the editor issue in the 5.2 tree.  But a crash we will it it can be reproduced!

[peterlaursen]

no .. this is a SQLyog bug.

this SQL is valid:

Code:

alter table `test`.`a` add column `newcolumn` double UNSIGNED NULL after `lastcolumn`;

MySQL docs:

http://dev.mysql.com/doc/refman/5.0/en/numeric-types.html

.. does not mention anything particular about UNSIGNED and FLOATs and DOUBLEs

Also you can alter a negative number from SQLyog, svae, press “refresh” and it shows '0 (zero) – so the UNSIGNBED clause works with MySQL 5.0!

there could be some issue with old MySQL versions however … we need a littletime to research on this!

[peterlaursen]

1) ALWAYS tell what SQLyog version you are using!

2) did you read and understand this:

http://webyog.com/faq/34_102_en.html

3) please show the returns of the statement

Code:

SHOW VARIABLES LIKE '%character%';

4) We cannot really relate to the crash report before you replied to the other questions!

[peterlaursen]

We have no such plans.

The MySQL and Postgresql architecture and the SQL dialects are so much different that it would be a very big task.

[peterlaursen]

We need a test case.

A structure-only dump (no data required) of SOURCE and TARGET where it fails

Could you create such test case?

Zip the files and attach here (or create a ticket if you do not want to expose it in public).

[peterlaursen]

http://www.webyog.com/forums//index.php?sh…amp;#entry12687

says:

Quote:

Password (and the passphrase for SHH key authentication) are now encrypted in the 'sqlyog.ini' file. The complete code handling passwords is completely rewritten. As a consequense you will need to re-enter both the MySQL Server password ………..

 

[Author]

Posts