3 ms·
You're right; MySQL is currently throwing an error (and therefore we don't even send the item to the Algolia engine). Gonna take a look tomorrow or the day afte
by redox_ 13y ago
You're right; MySQL is currently throwing an error (and therefore we don't even send the item to the Algolia engine). Gonna take a look tomorrow or the day after.
Mysql2::Error: Incorrect string value: '\xF0\x9D\x96\x86 m...' for column 'text' at row 1:
Thank you for the bug report ;)
- xroche 13y ago"utf8" in mysql is limited to 16-bit range (!) ; see http://golem.ph.utexas.edu/~distler/blog/archives/002539.html http://golem.ph.utexas.edu/~distler/blog/archives/002539.htm... - basically, you need to use "utf8mb4" (http://dev.mysql.com/doc/refman/5.5/en/charset-unicode-utf8mb4.html http://dev.mysql.com/doc/refman/5.5/en/charset-unicode-utf8m...)
- redox_ 13y agoI switched our database encoding to `utf8mb4` (thank you xroche), let's understand why the text is now truncated in https://hn.algolia.io/#!/story/forever/prefix/0/unicode%20text%20variants https://hn.algolia.io/#!/story/forever/prefix/0/unicode%20te... :)