Re: data type and Character set for DUTCH language
Posted by: Rick James
Date: July 28, 2013 03:23PM

\xE9 is é (e-acute) in latin1
See http://mysql.rjweb.org/doc.php/charcoll#8_bit_encodings (any many other places on the web).

These threads also had 1366 errors
http://forums.mysql.com/read.php?10,527295,527295
http://forums.mysql.com/read.php?103,418508,418508

Your problem _probably_ comes from an inconsistency.
You client has latin1 (apparently), so SET NAMES latin1 is needed.
The CREATE TABLE implies that the table is utf8. That inconsistency _is_ handled by MySQL -- it will convert between latin1 and utf8 as data is transferred.

If you had SET NAMES utf8, then error 1336 would (I think) happen. This is because SET NAMES utf8 is declaring that \xE9 is a utf8-encoding, which it is not.

VARBINARY (and BLOB) is happy to take any bytes you give it. But that leaves it up to the client(s) to 'do the right thing'.

Based on what you have said so far...
* Client should do SET NAMES latin1 after connecting.
* CREATE TABLE ... VARCHAR ... utf8

However, if you want the ij ligature (ij), which is not available in latin1, you need to switch to utf8 encoding throughout your system (clients and servers), and so SET NAMES utf8. This would allow intermixing Cyrillic, Greek, Chinese, etc, with the Dutch.

Options: ReplyQuote


Subject
Views
Written By
Posted
Re: data type and Character set for DUTCH language
2491
July 28, 2013 03:23PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.