Alex Brainman

> Is there any planned ETA for merging it into production? I would like to understand what is the problem that this PR fixes first. Can you provide a small...

> bitbucket.eng.zebrium.com/zsw/zwsd/vendor/github.com/alexbrainman/odbc.(*BindableColumn).Value(0xc4205afa80, 0x7f76c00008c0, 0x61, 0x7cf2e0, 0xc4204031e8, 0x0, 0x0) /home/alan-y/go/src/bitbucket.eng.zebrium.com/zsw/zwsd/vendor/github.com/alexbrainman/odbc/column.go:260 +0x3e7 Current version of column.go line 260 https://github.com/alexbrainman/odbc/blob/2d7d0e45c7870320611501683ca6073a0d9dfeed/column.go#L260 does not have panic. And you did not say how do I reproduce...

Why do you need this function? How it is helpful to you? Who will maintain this function in the future? Imagine that I tomorrow I will add more column types....

Thank you for explaining. I don't see your changes useful to me. The change looks just like an extra code that I have to maintain for no benefit to me....

> I'm a plus one on wanting this implemented. However I don't think this actually goes far enough. Sorry for pushing this back. But I have no free time to...

I always install unixODBC using OS package manager, so I do not know the answer to your question. But, I suspect, you could change the source to specify whatever directory...

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

> 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...

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