ASTERISK-19334: Adaptive CDR via ODBC driver can't handle UTF8-type fields in database

[Home]

Summary: ASTERISK-19334: Adaptive CDR via ODBC driver can't handle UTF8-type fields in database

Reporter: Igor Nikolaev (microlana) Labels:

Date Opened: 2012-02-10 01:10:25.000-0600 Date Closed: 2012-02-28 15:54:19.000-0600

Priority: Minor Regression? No

Status: Closed/Complete Components: CDR/cdr_adaptive_odbc

Versions: 10.1.0 Frequency of
Occurrence Constant

Related
Issues:

Environment: OS version: OpenSuSe 12.1 Installed packages: Source repository: openSUSE-12.1-12.1-1.4 unixODBC: x86_64 version 2.2.12-212.1.2 MyODBC-unixODBC: x86_64 version 5.1.8-4.1.2 Target MySQL server: 5.1.46-log MySQL-encoding: UTF-8 Unicode (utf8) s7*CLI> core show version Asterisk 10.1.0 built by root @ ss7 on a x86_64 running Linux on 2012-02-07 08:29:27 UTC Attachments: ( 0) cdr_adaptive_odbc.patch

Description: CDR not update any CHAR/VARCHAR/TEXT fields on database.

Comments: By: Igor Nikolaev (microlana) 2012-02-10 01:12:13.498-0600

Enable WCHAR-type fields processing via ODBC CDR module.
By: Jonathan Rose (jrose) 2012-02-28 15:45:16.568-0600

The patch was really sensible, so I went ahead and committed it, but out of curiosity, what type of database where you using exactly behind ODBC? With pgsql, I couldn't actually reproduce any problems while using a number of common utf8 characters.