Hello.
I see nothing wrong in your settings. The problem could be that
special characters in windows have different codes than in latin1,
as was mentioned by Dusan Pavlica. When you'll debug this issue
try to keep the table's and column's encoding the same as in SET NAMES,
you could lose some information during conversions.
Javier Ballesteros Correa <[EMAIL PROTECTED]> wrote:
> Hi, Mr. Paharenko,
>
> Here are the results:
>
> character_set_client | latin1
> character_set_connection | latin1
> character_set_database | latin1
> character_set_results | latin1
> character_set_server | latin1
> character_set_system | utf8
>
> character_sets_dir | C:\Archivos de
> programa\MySQL\MySQL Server 4.1\share\charsets/
>
> collation_connection | latin1_swedish_ci
> collation_database | latin1_swedish_ci
> collation_server | latin1_swedish_ci
>
>
> Create Table: CREATE TABLE `datos` (
> `id_user` tinyint(3) unsigned NOT NULL auto_increment,
> `nombre` varchar(55) NOT NULL,
> `dni` varchar(10) NOT NULL,
> `nacimiento` date NOT NULL,
> `direccion` varchar(255) NOT NULL,
> `telefono` varchar(9) NOT NULL,
> `desde` date NOT NULL,
> `hasta` date NOT NULL,
> `subcontrata` enum('No','Correos','Vanyera'),
> PRIMARY KEY (`id_user`)
> ) ENGINE=InnoDB DEFAULT CHARSET=latin1
>
> I have tried with the latin1_spanish_ci collation, but
> the problem remains.
>
>
>
>
>
> ______________________________________________
> Renovamos el Correo Yahoo!: $250 MB GRATIS!
> Nuevos servicios, m$s seguridad
> http://correo.yahoo.es
>
--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Gleb Paharenko
/ /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED]
/_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET
<___/ www.mysql.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
