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
{{ message }}
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.
An encoding config option would be useful for that. However, we should not change the default encoding to UTF-8 as that would require all strings we use in DB queries to be valid UTF-8 strings. This includes object names, comments, commands, etc. and will likely break (e.g. when users create comments with ISO-8859-1 characters that are outside the ASCII range (0-127)).
This issue has been migrated from Redmine: https://dev.icinga.com/issues/5696
Created by mfrosch on 2014-02-26 08:14:39 +00:00
Assignee: (none)
Status: New
Target Version: Backlog
Last Update: 2015-08-04 18:58:29 +00:00 (in Redmine)
I noticed a weird behavior, maybe a bug with libdbi itself.
IDO2DB connects to a database, specifying encoding as "auto".
This results in Debian wheezy and jessie to the following result:
hostgroup_alias: Testsörver
status.dat: Testsörver
IDO: Testsörver
Looks like the database connection thinks its input is latin, and converts it to unicode.
Question is, how can we investigate this, is it a bug in libdbi or our problem?
db.c
The text was updated successfully, but these errors were encountered: