[unixODBC-dev] UNICODE and unixODBC

Nick Gorham nick at lurcher.org
Mon Sep 5 08:30:59 BST 2005


Igor Korot wrote:
> Igor Korot wrote:
> 
> 
>>I want to use UNICODE, so I wont have a problem with the international characters,
> 
> but I want to access the database at the same time.
> 
>>>Do you think it would be possible with the --enable-unicode being "of"?
>>> 
>>>
>>
>>Ok, but you will only get international chars from the database if it 
>>supports UNICODE.
> 
> You mean the DB support UNICODE or the driver for that DB will convert it? Just to make sure: if I have a German umlaut in the DB, and the wxGTK is compiled without UNICODE support, but the driver will support UNICODE, what I will receive? Will I get the umlaut, or the ASCII symbols for the umlaut codes? Or it will depend on the driver UNICODE support?
> 
Its entirly down to the driver.

> 
>>>Also, if I put the line
>>>
>>>#define SQLTCHAR wchar_t
>>>
>>>do you think it will solve the compilation errors?
>>>
>>> 
>>>
>>
>>I doubt it. I would ask the wx folk, its not something under the control 
>>of unixODBC. You could try changing the definition of SQLTCHAR in 
>>sqltypes to match the above, that may work.
> 
> You mean in the file sqltypes.h put something like
> 
> #define SQLTCHAR wchar_t
> 
> ? But then the problem would be: is it safe from the unixODBC point of view? Am I gonna break anything there? I mean the latest unixODBC is prety stable, so just to make sure I won't break anything by doing this...
> 

Well, the best solution would be to get the wx code fixed to match what 
the driver manager does.

-- 
Nick



More information about the unixODBC-dev mailing list