Open tpng opened 7 years ago
Thank you for creating this issue. I need to think about this problem before I consider your fix.
Alex
[varchar_column] varchar(200) COLLATE Chinese_Taiwan_Stroke_CI_AS
Shouldn't varchar(200) be nvarchar(200) here?
Alex
If nvarchar is used, everything works correctly. But the column is on a legacy table so I can't change the column type to nvarchar easily.
I can't change the column type to nvarchar easily
I do not see how I can help you here. I do not know enough about storing Chinese in varchar columns. I am not even sure it is possible.
Alex
It seems storing Chinese in varchar column depends on the server code page setting. I understand the difficulty in supporting this, so feel free to close this if this is not feasible.
Workarounds for others encountering the same issue: cast varchar column to nvarchar in the query, e.g.
select * from testcase where cast(varchar_column as nvarchar(200)) = ?
I do not know enough about this matter. Maybe others will help you here.
I did test (on windows and linux) that https://github.com/alexbrainman/odbc/pull/82 does not help this issue.
Alex
Thanks for the nice package though, it helps so much in my daily work! I have closed #82 since the issue is more complicated then I originally thought.
same problem for cp1251 codepage - varchar columns not converted to unicode and transferred to &interface{} variable as []byte in cp1251 codepage (but i waiting for utf8)
SQL Server 2000
Test table:
Go program: