Re: Linux Unicode character size - Mailing list pgsql-odbc

From FabijanicA@nucorsteel.com
Subject Re: Linux Unicode character size
Date
Msg-id OF6A3A9F31.766BF1F7-ON852573C5.0066B122-852573C5.0066FBF3@nucorsteel.com
Whole thread Raw
In response to Re: Linux Unicode character size  (Andrei Kovalevski <andyk@commandprompt.com>)
List pgsql-odbc

Andrei Kovalevski <andyk@commandprompt.com> wrote on 01/03/2008 12:34:58 PM:

>     So, if you are building unixODBC with SQL_WCHART_CONVERT - you
> should specify the same option for psqlodbc.
> If SQLWCHAR = wchar_t, then  sizeof(SQLWCHAR) = 4. If SQLWCHAR =
> unsigned short, then sizeof (SQLWCHAR) = 2. SQLWCHAR on Windows is
> always 2 bytes wide.


Andrei,

Thank you for the reply. I am aware of the above. But, since I have a binary distro (Ubuntu), I am not building either. To be platform transparent, it's simplest to keep things to be 2 bytes wide (which, AFAICT, is default for unixODBC) and I was wondering what is the "default" (if there is such a thing) for psql. Currently, my problem is that I get SQL_NO_DATA from SQLDriverConnectW when I pass UTF-16 string.

Alex

-----------------------------------------------------------------------------------------------------------------------------------------
CONFIDENTIALITY NOTICE This e-mail contains privileged and confidential information which is the property of Nucor, intended only for the use of the intended recipient(s). Unauthorized use or disclosure of this information is prohibited. If you are not an intended recipient, please immediately notify Nucor and destroy any copies of this email. Receipt of this e-mail shall not be deemed a waiver by Nucor of any privilege or the confidential nature of the information.

pgsql-odbc by date:

Previous
From: Andrei Kovalevski
Date:
Subject: Re: Linux Unicode character size
Next
From: "Joost Kraaijeveld"
Date:
Subject: SQLDescribeCol returns wrong columnsize for macaddress ?