You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hmm, weird...I don't manually set the encoding on those tables in the migrations. Maybe I should, I think Phinx can do that. I'd have to check into it though. I hadn't really tested much yet with other character sets or languages.
Please look at my pull request #25. I'm not sure if I created pull request right - didn't do it before, hehe; I just clicked some buttons here and there and something happened, I hope right things happened.
Regarding description being truncated - please also see #23, about varchar(20): word "Получатели" consists exactly of 10 chars, which, without charset=utf-8, converts to "Получатели" consisting of 20 chars, second word doesn't fit into description field, being lost. With charset=utf-8 both words fit well.
Here is the code:
As you can see, there are two words in description.
The PHP script is written in UTF-8.
When I look into the "groups" table, I see this: "Получатели"
It is one word stored in an unknown way for me.
var_dump() gives me this:
It manages to decode the garbage back to cyrillic, but the second word is lost anyway.
Users cyrillic UTF data is stored in the same way - as garbage.
I think UTF-8 should be stored as UTF-8 without any magic.
BTW, groups table has right encoding of "utf8_general_ci".
The text was updated successfully, but these errors were encountered: