search

Icinga / icinga-notifications-web

Icinga Notifications Web — Manage incidents and who gets notified about them how and when
GNU General Public License v2.0
11 stars 0 forks source link

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

Open ChristophHCB opened 1 month ago

ChristophHCB commented 1 month ago

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: image

So please add this to the documentation.

oxzi commented 1 month ago

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 commented 1 month ago

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 utf8working when playing around with this issue for some time. But yeah you are right. Works fine with utf8mb4too (already changed it).

nilmerg commented 1 month ago

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.