summaryrefslogtreecommitdiff
path: root/wiki
diff options
context:
space:
mode:
Diffstat (limited to 'wiki')
-rw-r--r--wiki/mysql/choose-something-else.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/wiki/mysql/choose-something-else.md b/wiki/mysql/choose-something-else.md
index 795dcc7..ceb3966 100644
--- a/wiki/mysql/choose-something-else.md
+++ b/wiki/mysql/choose-something-else.md
@@ -65,9 +65,9 @@ familiar with other SQL implementations).
states](http://dev.mysql.com/doc/refman/5.5/en/server-sql-mode.html), making
it harder to carry expectations from manual testing over to code or from
tool to tool.
-* MySQL uses non-standard and rather unique interpretations of several common
- character encodings, including UTF-8 and Latin-1. Implementation details of
- these encodings within MySQL, such as the `utf8` encoding's MySQL-specific
+* MySQL recommends UTF-8 as a character-set, but still defaults to Latin-1. The implimentation
+of `utf8` up until MySQL 5.5 was only the 3-byte [BMP](http://en.wikipedia.org/wiki/Basic_Multilingual_Plane#Basic_Multilingual_Plane). MySQL 5.5 and beyond supports a 4-byte `utf8`, but confusingly must be set with the character-set `utf8mb4`. Implementation details of
+ these encodings within MySQL, such as the `utf8`
3-byte limit, tend to leak out into client applications. Data that does not
fit MySQL's understanding of the storage encoding will be transformed until
it does, by truncation or replacement, by default.