Re: MAC OSX copy_and_convert_field bug for SQL_W_CHAR - Mailing list pgsql-odbc

From Dave Page
Subject Re: MAC OSX copy_and_convert_field bug for SQL_W_CHAR
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E4CC3617@ratbert.vale-housing.co.uk
Whole thread Raw
In response to MAC OSX copy_and_convert_field bug for SQL_W_CHAR  ("Joel Kiger" <kiger.joel@cimcor.com>)
List pgsql-odbc

> -----Original Message-----
> From: pgsql-odbc-owner@postgresql.org
> [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Joel Kiger
> Sent: 20 October 2005 19:01
> To: Dave Page; pgsql-odbc@postgresql.org
> Subject: Re: [ODBC] MAC OSX copy_and_convert_field bug for SQL_W_CHAR
>
> I has not too much luck with version 08.01.0005, but however
> by commenting
> out #define HAVE_LOCALE_H 1 in config.h it does seem to be
> owrking for the
> time being, at least with ASCII characters.
>

Err, right - That's definitely not the right fix, but if it help you out
for now...

I've just tried a quick compile on Panther, and Unicode definitely isn't
supported (there is no sqlucode.h for example), though I see that Tiger
does have a newer iODBC which does have that header.

It also needs to link with libiodbcinst (for
SQLGetPrivateProfileString/SQLWritePrivateProfileString). Peter, I'm
assuming that either no-one uses iODBC, or that this is a Mac specific
thing. Is there a painless way to get autoconf to add the library if
needed?

Finally, I'm getting warnings about multiple definitions of some MD5
functions (I guess it's finding them in libpq, as that's where they were
borrowed from). I guess that might not be an issue at all if the libpq
exports are cleaned up in the future, but in the meantimeI don't think
there's an actual problem anyway (I'm sure Peter or Tom will correct me
if I'm wrong about that :-p )/

I can't look at this for at least a couple of weeks unfortunately
though.

Regards, Dave.

pgsql-odbc by date:

Previous
From: "Joel Kiger"
Date:
Subject: Re: MAC OSX copy_and_convert_field bug for SQL_W_CHAR
Next
From: Zlatko Matić
Date:
Subject: Re: versions of oDBC driver