Bug #28817 Problems with characters Latin1
Submitted: 31 May 2007 20:42 Modified: 12 Dec 2007 10:35
Reporter: Bruno Nunes Email Updates:
Status: Not a Bug Impact on me:
None 
Category:Connector / ODBC Severity:S3 (Non-critical)
Version:5.1 OS:Any
Assigned to: CPU Architecture:Any
Tags: accentuation, Latin1

[31 May 2007 20:42] Bruno Nunes 
Description:
Previously, on 3.51, I could sent to database words with accentuation, like "SÃO PAULO" or "JACAREÍ"...

Now I have the Windows Vista and with the problems with 3.51 version, I downloaded the 5.00 Beta version.

Then when I tried to update my database, I see this words like that: "SÃO PAULO" AND "JACAREÍ"

How to repeat:
Just try to update in a latin1 database a word with accentuation, like 'á', 'é', 'ã', 'ú', 'ç', and others...

Suggested fix:
Just see what is happening...

Examples of words:
"São Paulo"
"Saúde"
"Arujá"
"Programação"
[4 Jun 2007 16:34] Jess Balint 
Bruno,

MySQL Connector/ODBC v5 is setup to use Unicode by default. What is the environment for your application? Is it ASP or Visual Basic? Also, we have fixed many issues in the nightly builds. Please feel free to download the most recent build and let us know if it solves your problem:

http://downloads.mysql.com/snapshots/mysql-connector-odbc-5.0/
[5 Jun 2007 18:23] Bruno Nunes 
Well... not resolved yet...

I am updating from my Cobol program, to my PHP site in internet...

I'll trying here... Thank you!!!
[12 Jun 2007 14:18] Tonci Grgin 
Bruno, what happens if first SQL statement you issue from your code is "SET character_set_results=latin1?
[12 Jul 2007 23:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[13 Jul 2007 8:23] Tonci Grgin 
Bruno, did you solve your problem? What happens if you use MyODBC 3.51.16?
[13 Aug 2007 23:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[22 Oct 2007 17:33] Susanne Ebrecht 
I can reproduce this with using MyODBC 5.1.
Also it seems, that some ISO-8859-1 characters won't be inserted in the right way.
[22 Oct 2007 17:34] Susanne Ebrecht 
test for this

Attachment: bug28817.c (text/x-csrc), 4.42 KiB.
[22 Oct 2007 18:24] Susanne Ebrecht 
Seems, my test program was defect. I can't reproduce the update behaviour for all special signs.

But I figured out, there is a problem with some special ISO signs like the à from SÃO PAULO. The little ã works fine.

Also with the Cedile: The Ç won't work the ç works.
[22 Oct 2007 18:25] Susanne Ebrecht 
correct test

Attachment: bug28817_ok.c (text/x-csrc), 4.31 KiB.
[12 Dec 2007 1:28] Kent Boortz 
When I download the test program above, it is all UTF8,
not ISO8859-1. Does this really verify the problem the
user is having?
[12 Dec 2007 10:35] Susanne Ebrecht 
Sorry, this was my misstake, my test mixed USC2 and ISO.

This is not a bug. Please, make sure, when you use Latin1, that all in your enviroment is Latin1 compatible. This means, your screen/window/enviroment, in which you get the output should have Windows Codepage 1252 (ISO-8859) encoding. Also make sure, that all, that you insert into the database is written with that encoding.
Your Error description is a typical case of encoding mixes.

Many thanks for choosing MySQL.
[12 Dec 2007 10:37] Susanne Ebrecht 
the test with using really latin1

Attachment: bug28817.c.tar.gz (application/gzip, text), 1.34 KiB.