Missing information in docs: Database ressource Character Set needs to be utf8

[ChristophHCB]

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.

[oxzi]

Thanks for reporting this issue.

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.

[ChristophHCB]

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).

[nilmerg]

how did this happen?

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.

[nilmerg]

If the client (session) charset is not equal to that of the database, PHP's json_decode fails to parse a channel's config because translations contain non-ascii chars. So a fix for this needs to address two things:

• Correct handling in case config cannot be decoded. The form must not be valid in that case.
• Mention in the configuration documentation, that it might be necessary to set the character set of the resource to utf8 (utf8mb4 in case of MySQL/MariaDB) or change the default charset of the server.

[Al2Klimov]

[Al2Klimov]

Seriously speaking, we could at least default to a sane default where we know the latter. (IDO: latin1, Icinga DB and everything else: utf8, ...)