Skip site navigation (1) Skip section navigation (2)

Re: Unicode support

From: "Anoop Kumar" <anoopk(at)pervasive-postgres(dot)com>
To: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
Cc: <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: Unicode support
Date: 2005-08-31 05:08:58
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-odbc
Hi Dave,

Checking for the database encoding and calling the functions using the
appropriate flag seems to be fine.



> -----Original Message-----
> From: Dave Page [mailto:dpage(at)vale-housing(dot)co(dot)uk]
> Sent: Wednesday, August 31, 2005 3:07 AM
> To: Anoop Kumar
> Cc: pgsql-odbc(at)postgresql(dot)org
> Subject: Unicode support
> Hi Anoop and anyone else who might be interested,
> I've been thinking about how the Unicode support might be improved to
> allow the old 07.xx non-unicode style behaviour to work for those that
> need it. At them moment, when we connect using on of the wide connect
> functions, the CC->unicode flag is set to true. This only affects a
> options, such as pgtype_to_concise_type()'s mapping of PG types to SQL
> types.
> It seems to me that perhaps we should set CC->unicode = 1, only upon
> connection to a Unicode database. Anything else, we leave it set to 0
> that it always maps varchars etc to ANSI types, and handles other
> encodings in single byte or non-unicode multibyte mode (which worked
> fine in 07.xx where those encodings where appropriate, such as SJIS in
> Japan). This should also help BDE based apps, which further research
> shown me are broken with Unicode columns in SQL Server and Oracle as
> well as PostgreSQL (search unicode + BDE on Google Groups for more).
> Am I seeing a possible improvement where in fact there isn't one, or
> missing some obvious downside?
> Regards, Dave.

pgsql-odbc by date

Next:From: Anoop KumarDate: 2005-08-31 05:51:08
Subject: Re: changed behavior in libpq odbc driver
Previous:From: Anoop KumarDate: 2005-08-31 04:58:02
Subject: Re: changed behavior in libpq odbc driver

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group