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
This has cost me quite some time to figure out. When the Character Set of the database ressource is not set to utf8 you only get the following error when creating a Channel:
So please add this to the documentation.
The text was updated successfully, but these errors were encountered:
Which charset was configured and how did this happen? The schema defines CHARSET=utf8mb4 COLLATE=utf8mb4_bin for each table, unless I am missing something.
I had no charset configured in the beginning because it was not mentioned in the docs when setting up the ressource. I somehow missed to take a look into the schema and I stumbled across utf8 working when playing around with this issue for some time. But yeah you are right. Works fine with utf8mb4 too (already changed it).
What the schema defines is not important while reading from it. By configuring the charset in the resource configuration this way, the session charset matches the schema's and data is transferred 1:1.
This has cost me quite some time to figure out. When the
Character Set
of the database ressource is not set toutf8
you only get the following error when creating aChannel
:So please add this to the documentation.
The text was updated successfully, but these errors were encountered: