From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | <lothar(dot)behrens(at)lollisoft(dot)de>, <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: VARCHAR, CHAR types changed ? |
Date: | 2005-11-25 12:31:27 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E4E7E37B@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
> -----Original Message-----
> From: pgsql-odbc-owner(at)postgresql(dot)org
> [mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of
> lothar(dot)behrens(at)lollisoft(dot)de
> Sent: 25 November 2005 12:09
> To: pgsql-odbc(at)postgresql(dot)org
> Subject: [ODBC] VARCHAR, CHAR types changed ?
>
> Hi,
>
> I am trying the new, or most actual database under Windows 2000 (8.0).
> This driver don't let
> my test application crash. Compared to the old driver and Database
> (07.03.0200), my
> other application should run too.
>
> But I get some unexplainable changes in supported types. My
> VARCHAR(100) and even,
> if I change it to CHAR(100), isn't any more supported.
>
> (The error message from me reports -8 as DataType)
>
> What has been changed ?
Looks like you are using the unicode version of the driver (-8 is
SQL_C_WCHAR). You could either:
- Change to the ANSI driver, which should never return SQL_C_WCHAR.
- Update your code to handle Unicode data.
- Update your code to recognise SQL_C_WCHAR, but then request SQL_C_CHAR
data instead.
I would plump for the first option, unless you want to support Unicode.
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | lothar.behrens@lollisoft.de | 2005-11-25 13:20:49 | Re: VARCHAR, CHAR types changed ? |
Previous Message | lothar.behrens@lollisoft.de | 2005-11-25 12:08:47 | VARCHAR, CHAR types changed ? |