Guys, maybe this is the problem:
DBD::ODBC assumes a default column bind type of SQL_WVARCHAR with Unicode builds if SQLDescribeParam is unavailable. Accepting this default setting results in
DBD::ODBC::st execute failed: [unixODBC][FreeTDS][SQL Server]Invalid
data type (SQL-HY004) at ./charset.pl line 34.
for the INSERT. Explicitly setting this to SQL_VARCHAR makes everything work again – except character set conversion. Maybe a side
effect is that character set conversion will be disabled as well?
When enabling DBD::ODBC tracing with
DBI->trace(DBD::ODBC->parse_trace_flags('odbcconnection|odbcunicode'));
I'll get
SQL_DBMS_NAME = Microsoft SQL Server
SQLMoreResults supported: 1
SQLDescribeParam supported: 0
SQLDescribeParam supported: 0
unicode support = 1
Processing non-utf8 sql in unicode mode
Anys ideas are appreciated...
Regards,
Stephan
smime.p7s
Description: S/MIME Cryptographic Signature
