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

Re: ANSI and Unicode driver

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Peter Eisentraut" <peter_e(at)gmx(dot)net>,<pgsql-odbc(at)postgresql(dot)org>
Subject: Re: ANSI and Unicode driver
Date: 2006-02-20 16:52:20
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E40103E24D@ratbert.vale-housing.co.uk (view raw or flat)
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 Peter Eisentraut
> Sent: 20 February 2006 16:05
> To: pgsql-odbc(at)postgresql(dot)org
> Subject: [ODBC] ANSI and Unicode driver
> 
> So really, what is the difference between the ANSI and the 
> Unicode driver?  
> The Unicode driver sets the client encoding to UTF-8, but 
> does that mean that 
> the client application has to use UTF-8 or does the driver 
> manager convert 
> that?  What do you use if you have, say, a Chinese 
> application.  Or a Latin 1 
> application but a UTF-8 database?  How does this work?  I'm confused.

The Unicode driver adds a bunch of unicode-specific APIs. Our ANSI
driver can handle Unicode data as multibyte strings as well, but without
the Unicode APIs that many non-multibyte aware versions of Windows
require (if that makes sense!).

Regards, Dave. 

Responses

pgsql-odbc by date

Next:From: Hiroshi InoueDate: 2006-02-20 17:09:59
Subject: Re: Building the psqlODBC enhanced branch (Linux)
Previous:From: Dave PageDate: 2006-02-20 16:47:18
Subject: Re: Building the psqlODBC enhanced branch (Windows)

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