[ODBC-22] ODBC report error about Illegal mix of collations Created: 2015-05-13  Updated: 2015-05-13  Resolved: 2015-05-13

Status: Closed
Project: MariaDB Connector/ODBC
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Blocker
Reporter: mikeca Assignee: Lawrin Novitsky
Resolution: Duplicate Votes: 0
Labels: None
Environment:

ALU product

Attachments: Text File maodbc.log    

 Description   

Here is the log from our product.
00001(00143),00000(00000) 0x00000001 05-13 13:39:47.251 16312: Adding sfw-peernet for TGP to Tables
../src/DBTrkTbls.c:567
00001(00143),00000(00000) 0x00000001 05-13 13:39:47.251 16312: getApi(../src/GetDBApi.c:683): ERROR - SQLExecDirect Failed - [ma-2.0.7][10.0.14-MariaDB-log]Illegal mix of collations (latin1_general_cs,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation '=' ODBC Error/Warning = HY000, MySQL Error/Warning = 1267, ConnStr = socket=/opt/MySql/mysqld/mysql.sock;uid=PERM_DBP_SOFT;database=SoftSwitch;OPTIONS=4;, plx Caller's plxThreadID = 16312 & plxThreadName = dbp:Pool

00001(00143),00000(00000) 0x00000001 05-13 13:39:47.252 16312: Get sfwPinhole: tgn:11, numPinhole:0
00001(00143),00000(00000) 0x00000001 05-13 13:39:47.252 16312: RAW DB ERROR is 1267 at: ../src/DBPCommon.c:74

 Comments   
Comment by Lawrin Novitsky [ 2015-05-13 ]

This looks like a duplicate of ODBC-6
And thus most probably is not a bug. Pleas try to add CHARSET=latin1 to your connection string. I am closing the issue for now. Please re-open it if the issue persists.

Generated at Thu Feb 08 03:25:39 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.