Without detecting these types, cel_odbc blows up when the character
set for the table is utf8. This also wraps cdr_adaptive_odbc's use of
those types in the HAVE_ODBC_WCHAR #ifdef seen in other parts of the
code.
........
Merged revisions 358435 from http://svn.asterisk.org/svn/asterisk/branches/1.8
........
Merged revisions 358436 from http://svn.asterisk.org/svn/asterisk/branches/10
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@358437
65c4cc65-6c06-0410-ace0-
fbb531ad65f3
case SQL_CHAR:
case SQL_VARCHAR:
case SQL_LONGVARCHAR:
+#ifdef HAVE_ODBC_WCHAR
case SQL_WCHAR:
case SQL_WVARCHAR:
case SQL_WLONGVARCHAR:
+#endif
case SQL_BINARY:
case SQL_VARBINARY:
case SQL_LONGVARBINARY:
case SQL_CHAR:
case SQL_VARCHAR:
case SQL_LONGVARCHAR:
+#ifdef HAVE_ODBC_WCHAR
+ case SQL_WCHAR:
+ case SQL_WVARCHAR:
+ case SQL_WLONGVARCHAR:
+#endif
case SQL_BINARY:
case SQL_VARBINARY:
case SQL_LONGVARBINARY: