forums › forums › SQLyog › Using SQLyog › Database Synchro Wizard Changes Accented Characters With "?"
- This topic is empty.
-
AuthorPosts
-
-
November 9, 2007 at 6:28 pm #10622Julian VidalParticipant
Hi,
I'm doing a one-way synchro of a MySQL database and the accented characters are replaced with question marks (“?”) in the destination database.
The source server is: 4.0.27-log (Linux)
Destination server is: 4.1.22-community-nt (Windows)
What could be the problem?
Here is the schema (as created by PhpMyAdmin) for both servers:
Source schema:
Code:CREATE TABLE `destinations` (
`destinationId` int(10) unsigned NOT NULL auto_increment,
`name_spa` varchar(100) NOT NULL default '',
`name_eng` varchar(100) NOT NULL default '',
`minDays` smallint(2) NOT NULL default '0',
`messageId` int(10) unsigned NOT NULL default '0',
`extraTax` float(8,2) NOT NULL default '0.00',
`extraTaxType` enum('%',' ) NOT NULL default '%',
`tax` float(8,2) NOT NULL default '0.00',
PRIMARY KEY (`destinationId`)
) TYPE=MyISAM;Destination schema:
Code:CREATE TABLE `destinations` (
`destinationId` int(10) unsigned NOT NULL auto_increment,
`name_spa` varchar(100) collate latin1_general_ci NOT NULL default '',
`name_eng` varchar(100) collate latin1_general_ci NOT NULL default '',
`minDays` smallint(2) NOT NULL default '0',
`messageId` int(10) unsigned NOT NULL default '0',
`extraTax` float(8,2) NOT NULL default '0.00',
`extraTaxType` enum('%',' ) collate latin1_general_ci NOT NULL default '%',
`tax` float(8,2) NOT NULL default '0.00',
PRIMARY KEY (`destinationId`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1 COLLATE=latin1_general_ci; -
November 10, 2007 at 12:14 am #25254peterlaursenParticipant
Please tell the program version you are using!
And please also try 6.12 – such issue when syncing between 4.0 and 4.1 was fixed in this release.!
-
November 10, 2007 at 6:18 am #25255Julian VidalParticipantpeterlaursen wrote on Nov 9 2007, 09:14 PM:Please tell the program version you are using!
And please also try 6.12 – such issue when syncing between 4.0 and 4.1 was fixed in this release.!
You were right! I was using an outdated version! You guys keep updating this so often (fortunately) that it's hard to keep track.
Thanks for the info. Everything is working fine now.
-
-
AuthorPosts
- You must be logged in to reply to this topic.