distal-attribute
distal-attribute
distal-attribute
distal-attribute

problem on exporting

markzzz posted 4 years ago in General
Hello! I have this kind of table :

CREATE TABLE `users` (
`id` INT(11) UNSIGNED NOT NULL AUTO_INCREMENT,
`name` VARCHAR(255) NOT NULL,
`surname` VARCHAR(255) NOT NULL,
`nickname` VARCHAR(255) NOT NULL,
`password` VARCHAR(255) NOT NULL,
`mail` VARCHAR(255) NOT NULL,
`country` VARCHAR(255) NOT NULL,
`birthday` VARCHAR(255) NOT NULL DEFAULT '0000-00-00',
`accessres` TINYINT(11) UNSIGNED NOT NULL DEFAULT '0',
`admin` TINYINT(11) UNSIGNED NOT NULL DEFAULT '0',
`datereg` DATETIME NOT NULL DEFAULT '0000-00-00 00:00:00',
`forum_ban` TINYINT(11) UNSIGNED NOT NULL DEFAULT '0',
`last_access` DATETIME NOT NULL DEFAULT '0000-00-00 00:00:00',
PRIMARY KEY (`id`)
)
COLLATE='utf8_general_ci'
ENGINE=MyISAM
ROW_FORMAT=DEFAULT
AUTO_INCREMENT=209

How you can see, collate is utf8_general_ci. The problem is when I export this table using HeidiSql.
For example, if I have data such as "Krüger", it is exported as "Krüger" !

So there are some wrong in the export. What can I do? Cheers
markzzz posted 4 years ago
P.S. I'm using HeidiSql 6.0, and text I see is on scite text editor (but in fact everywhere, if I import, is showed as damaged text).
ansgar posted 4 years ago
You should watch for the data as it is stored in the table - I guess it's also broken there?
markzzz posted 4 years ago
No, the data in the table is correct. My whole application is utf8. When I export (and import) (also in localhost) the data go broken...
markzzz posted 4 years ago
The export is ok. Is the import with phpMyAdmin that is wrong (also, when I view the data with Scite text editor, but that's a software false). Sorry for this topic, not a HeidiSQL fault :)

ansgar posted 4 years ago
Oh, that's nice news. Thanks a lot for the update.

Please login to leave a reply, or register at first.